[sldev] About the Open Source Viewer

[Nicholaz Beresford]

My suggestion would be to make the JIRA the hub for
patches.  They could be posted with comments to not
immediately import them.  Or if the Lindens are not
sure about them they could say that they'd like to see
some pre-testing.

In any case, a patch running in a homebrew for some
time could be some sort of seal of approval for less
than trivial patches.

Maybe a JIRA state for issues like "in beta testing",
could offer more clarity to the process.

Just an idea though.


Nick


Second Life from the inside out:
http://nicholaz-beresford.blogspot.com/


Kamilion wrote:
> On 7/16/07, Dzonatas <dzonatas at dzonux.net> wrote:
>> You are correct. The QA bit is the higher priority of the effort.
>>
>> I'm still wonder what to do with those that have signed agreements that
>> want to submit source for review or for a test before a jira issue seems
>> practical.
> 
> Perhaps we should separate builds into 'stable' and
> 'testing/unstable', it seems to work for many other projects.
> 
> JIRA patches would end up in 'stable', and non-jira'd review/test
> patches can make it into testing/unstable.
> 
> When the patch ends up on JIRA, it could be moved over to stable.
> 
> Testing would likely be a subset of stable, making it a good place to
> test patches on top of the latest community patchset.
> 
>> In the end, yes, the jira serialization is very helpful and does help
>> make efforts become more official.
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html