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

Matthew Buckett matthew.buckett at oucs.ox.ac.uk
Mon Sep 19 02:56:19 PDT 2011


On Fri, Sep 16, 2011 at 11:01 PM, Anthony Whyte <arwhyte at umich.edu> wrote:
> 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.

I think getting people to focus on fixing bug by stopping new features
going into trunk is the right thing todo, however I'm concerned that
doing this for 3 months may be a little long.

Sadly for me Sakai work come second to local development/deployments
so I have to fit any work around local upgrades. At the moment I'm
moving Oxford to 2.8, out of this come patches which are applicable
for trunk and if they sit in Jira for months they tend to get
ignored/forgotten and then they become out of date.

-- 
  Matthew Buckett
  VLE Developer, LTG, Oxford University Computing Services


More information about the sakai2-tcc mailing list