[sakai2-tcc] [Building Sakai] Proposal: trunk is 2.9 from Sept-Jan until sakai-2.9.0-rc01 is ready for tagging

[Charles Hedrick]

This would help me significantly with lesson builder. I'd greatly prefer not to have to copy every change from trunk into the 2.9 branch. New work can easily be done in a branch.


On Sep 19, 2011, at 11:35 AM, Noah Botimer wrote:

> I think that this is generally a very good plan but I do share Matthew B's concern that the term may be long (but we don't really know now, as it depends on interest/capacity for new work beyond or despite our urging to focus on 2.9).
> 
> I have also long been supportive of the labels alpha, beta, and release candidate having useful meaning and criteria. In (maybe only) my mind, beta tags should indicate a relative stability and completeness. Perhaps the alpha-beta transition is a sensible moment to switch over to a release branch.
> 
> In any case, I am supportive of this and encourage us to move forward while keeping a finger on the pulse. There may be an indication of the "right time" before January, but it's a good ballpark for now.
> 
> As this appears to be a proposal rather than a vote, I'll bend my personal guidelines and combine an editorial with a ballot.
> 
> +1
> 
> Thanks,
> -Noah
> 
> On Sep 18, 2011, at 6:52 PM, Seth Theriault wrote:
> 
>> Anthony Whyte wrote:
>> 
>>> I propose that we reconsider this tradition and instead 
>>> adopt the following approach:
>>> 
>>> Non-indie trunk branches remain 2.9-SNAPSHOT until we are 
>>> ready to tag the first release candidate.  New work not 
>>> intended for 2.9.0 is performed in branches and held there 
>>> until we branch trunk for 2.9.  Indie projects also adopt 
>>> the same approach; trunk stays 2.9-oriented while new work 
>>> is performed in branches.  The release team cuts alpha/beta 
>>> QA tags from trunk.
>> 
>> +1.
>> 
>> Seth
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"