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

[Beth Kirschner]

I'd like to give the newly formed CLE Release Team the freedom & authority to develop the release process that we'll be using for Sakai 2.9. It sounds like there's a lot of support for maintaining trunk as a 2.9 "alpha" staging ground, with some reservations as to how long before we branch (I share this concern).

Someone needs to post an announcement to the sakai-dev list to introduce this new process to the whole Sakai developer community (or at least the ground rules as they stand). This could be me or perhaps Sam -- thoughts>?

- Beth

On Sep 19, 2011, at 2:51 PM, Matthew Jones wrote:

> I agree that patches shouldn't hang out on issues as those do get hard to merge. It would be better if svn branches were made if significant work was planned, as those are commits already in subversion are generally easier to merge and deal with than patches attached to jira. We'll still need to go through those and make sure to get them back into trunk though. The system isn't as good as something like git where you can flag a bunch of pull requests. Perhaps if the jira is flagged as "Feature Request" and the fix version is "2.10" then we'll be able to find them easier when the time comes. 
> 
> On Mon, Sep 19, 2011 at 5:56 AM, Matthew Buckett <matthew.buckett at oucs.ox.ac.uk> wrote:
> 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.
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc