[sakai2-tcc] Enhancement branch merge policy (end period) clarification

Matthew Jones jonespm at umich.edu
Thu May 19 09:08:43 PDT 2011


Hi Beth (and others),

A question came up about (enhancement) Branch Policy policy today [1] on the
RM call and I don't remember if there was ever an answer to it. It's was
regarding when the period for discussion is over and merging can be done.
Since you drafted the proposal maybe you remember if there was an answer?

* Yesterday JFL floated the request to merge SAK-14625 to 2.7.x. (Add group
section filter to dropbox) [2] Currently this has been met with silence
which is okay based on the policy. But there's nothing that states how much
time should pass before action can be taken to actually merge this. No
formal vote or discussion is required based on the proposal.

But when should it get actually merged if there are no objections? 1 week?
By the next release management call? When TCC chair says "Since there were
no objections to the request to merge SAK-14625 it shall be merged!" I don't
really have a great opinion on this. Minimum 1 week from email then made
official (in or out) at the next RM call seems like the best option to me?
Many of us on the RM call are also on TCC.

I plan to write up one for annotated URL (SAK-19369) for the next 2.7
release as well. I think these 2 were the first so far? There might be a few
more as we look to getting a 2.7.2 release out.

Thanks!

[1]
https://confluence.sakaiproject.org/display/TCC/Maintenance+Branch+Merge+Policy
[2] http://collab.sakaiproject.org/pipermail/sakai2-tcc/2011-May/001108.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20110519/9d6bf358/attachment.html 


More information about the sakai2-tcc mailing list