[sakai2-tcc] Policy for merging in bug fixes to maintenance branches
Kevin Chan
kevin at media.berkeley.edu
Mon Jun 20 11:49:03 PDT 2011
Thanks for the clarification.
I guess my next question is (since I jumped the gun with the wrong
process) what is the current process for merging in bug fixes to the
maintenance branches?
Kevin Chan
Operations Team
Educational Technology Services
UC Berkeley
On 6/16/11 2:18 PM, Beth Kirschner wrote:
> On Jun 15, 2011, at 6:14 PM, Kevin Chan wrote:
>> Is this email sufficient to satisfy the "public announcement" requirement?
>>
> I would say it is -- but I wonder if this process applies to this issue -- it's classified as a bug.
>
>> Can someone list the locations re: where the 2.7.x (for example) release notes are that requires updating?
>>
> I would suggest updating the release notes section of the JIRA (just select "edit").
>
> - Beth
>
>> Thanks,
>>
>> --
>> Kevin Chan
>>
>> Operations Team
>> Educational Technology Services
>> UC Berkeley
>>
>> _______________________________________________
>> production mailing list
>> production at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/production
>>
>> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
More information about the sakai2-tcc
mailing list