| Re: [sapphire-dev] Beyond 0.5 release |
Given this issue, I don’t think we can afford to wait a week before branching. We need to get started on 0.5.1 as soon as possible. To that end, I have created R_0_5_x branch and have versioned it as 0.5.1. HEAD is now versioned as 0.6.0. Both R_0_5_x and HEAD are now open for work in their respective releases. In terms of Hudson coverage, the existing job that we’ve been using for 0.5 is now covering the 0.5.1 release. https://hudson.eclipse.org/hudson/job/sapphire-0.5.x I have request a new job to be created for 0.6.x line, but that hasn’t happened yet. Thanks, - Konstantin From: sapphire-dev-bounces@xxxxxxxxxxx [mailto:sapphire-dev-bounces@xxxxxxxxxxx] On Behalf Of Konstantin Komissarchik I just found a major problem in the 0.5 release that will likely trigger a need for an early 0.5.1 release… Base property services can be hidden by deriving property https://bugs.eclipse.org/bugs/show_bug.cgi?id=382660 - Konstantin From: Konstantin Komissarchik [mailto:konstantin.komissarchik@xxxxxxxxxx] With 0.5 wrapped up and practically out of the door, we have a few things to go over… 1. In order to allow for an emergency respin of 0.5 prompted by the overall Juno release train need, we will go “hands off CVS” for about a week. So no commits until you hear from me. For now, stash any changes as patches attached to relevant bugs. Once I know that it is safe to do so, I will create 0.5.x branch for 0.5.1 work and HEAD will be open for 0.6 work. 2. The 0.5.1 release will be our Juno SR1 contribution. Bug fixes only. Absolutely nothing that would require any sort of migration steps or be otherwise incompatible with 0.5 release. To be released with the rest of Juno SR1 on September 28th. If we find a major issue in 0.5, we made elect to ship 0.5.1 early and create 0.5.2 to align with Juno SR1. 3. The 0.6 release will be our next feature release. It isn’t going to be tied to any release train, so the date is ours to set, but I’d like to return to quarterly feature releases, so let’s use September 28th as the working date. Same as 0.5.1 release. 4. Once dust settles after Juno release (about first or second week of July), we will do our CVS to git conversion. If you are still thinking “what’s git?”, now would be the time to find out. Let me know if there are any questions. - Konstantin |