[Opensim-dev] /branches/0.6.0-stable

Thu Nov 13 13:06:17 UTC 2008

So, since this was thought to be a good idea, I just copied the branch

/branches/0.6.0-stable from the tag /tags/0.6.0-release.

This branch is _only_ for applying post-release stability fixes - ie, no new user features, however minor.

Of course, this is a grey area, but I think you understand what the use of this branch is.
If somebody fixes something for trunk, whoever feeling inclined, should re-apply it to this branch as well, marking it clearly that they have done so.

We should be able to refer to this branch as "the most trustworthy revision for this version" at all times.

The difference form the 'tag' is that while the tag is 'stable' as in 'we know what's wrong, and you can trust us not to try to fix it', the branch is 'stable' as in 'if you find anything wrong with the tag, we might have fixed in the branch'.
Best regards,Stefan AnderssonTribal Media AB Join the 3d web revolution : http://tribalnet.se/ 

Date: Mon, 10 Nov 2008 15:00:28 +0200From: jpirkola at gmail.comTo: opensim-dev at lists.berlios.deSubject: Re: [Opensim-dev] Version Numbering Schemes+1
Excellent idea! 
--Jani
2008/11/10 Lc <lcc1967 at gmail.com>
+1
The first thing pple is looking is stabitlity then features...

On Mon, Nov 10, 2008 at 4:00 AM, Frisby, Adam <adam at deepthink.com.au> wrote:
Yeah, I do like that idea,+1Regards,Adam
> -----Original Message-----> From: opensim-dev-bounces at lists.berlios.de [mailto:opensim-dev-> bounces at lists.berlios.de] On Behalf Of Justin Clark-Casey> Sent: Sunday, 9 November 2008 6:50 PM> To: opensim-dev at lists.berlios.de

> Subject: Re: [Opensim-dev] Version Numbering Schemes>> Stefan Andersson wrote:> > +1 fo sho.> >> > Also, I would love if there was any kind of room for 'fortifying'> > a given version branch within the repo.> >> > I mean, when we tagged 0.6.0, could we have a branch that was> dedicated> > to just applying bug-fixes, and stabilizing fixes to?> >> > We've already said that we don't have the resources within the> project> > to do proper release cycle, but could we at least have somewhere for> > people who want to work on stability over features for a given> version?> > I know it would definitively help with my debugging motivation to> have> > one there - and believe it or not, but in the majority of cases, you> can> > actually apply the changes directly into the next version as well.> >> > How about a 0.6.0_fortified branch? Or some other numbering, perhaps?> >> > So, 0.6.1 would be bugfixes + ongoing development,> > 0.6.0_fortified would only be bugfixes, and done only by those who> > actually find the motivation to work on fortification of a given> version.>> This sounds like a good plan.  It would allow us to see if there is the> capacity or motivation to run both stable and> development streams (I don't think that we've reached the requires> level of maturity with the code yet).>> >> > Best regards,> > Stefan Andersson> > Tribal Media AB> >> > Join the 3d web revolution : http://tribalnet.se/> >> >> >> >> >> >> > ---------------------------------------------------------------------> ---> >> > From: adam at deepthink.com.au> > To: opensim-dev at lists.berlios.de> > Date: Sun, 9 Nov 2008 07:01:07 -0500> > Subject: [Opensim-dev] Version Numbering Schemes> >> >> > I'd like to propose switching our version numbering schemes to> something> > similar to how the Linux Kernel used to operate, whereby we have> > unstable and stable version numbers independent of each other.> >> >> >> > For instance,> >> >> >> > 0.6.0 is a stable release> >> > 0.6.1 is under development> >> > 0.6.2 is stable, etc.> >> >> >> >> >> > So as soon as we tag a stable release, we then increment the version> > number straight away up to an odd number to indicate that we're now> > working on potentially a not so stable version, when it returns to> > stability, we tag it again to an even number, add the tag & release,> > then increment back to an unstable one.> >> >> >> > This way, when users say they are using 0.6.X, we can quickly> determine> > if they are on a stable supported release, or bleeding edge.> >> >> >> > Thoughts?> >> >> >> > Adam> >> >> > ---------------------------------------------------------------------> ---> >> > _______________________________________________> > Opensim-dev mailing list> > Opensim-dev at lists.berlios.de> > https://lists.berlios.de/mailman/listinfo/opensim-dev>>> --> justincc> Justin Clark-Casey> http://justincc.wordpress.com> _______________________________________________> Opensim-dev mailing list> Opensim-dev at lists.berlios.de> https://lists.berlios.de/mailman/listinfo/opensim-dev_______________________________________________Opensim-dev mailing listOpensim-dev at lists.berlios.dehttps://lists.berlios.de/mailman/listinfo/opensim-dev_______________________________________________Opensim-dev mailing listOpensim-dev at lists.berlios.dehttps://lists.berlios.de/mailman/listinfo/opensim-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20081113/37da8be5/attachment-0001.html>