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

[Matthew Jones]

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20110919/429b40a3/attachment.html