[Building Sakai] Release management

[Steve Swinsburg]

Hi Paul,

File a ticket at http://jira.sakaiproject.org and choose the appropriate 'components' and 'affects versions'. Once it's created, check to see who it automatically gets assigned to. If its unassigned, then ping the sakai-dev list about it and someone might be able to take a look. Of course, if you are able to take a look yourself and provide a patch, this will generally speed things up.

Then, once its fixed in trunk, ensure the branch merge statuses are set, and if nothing, ping the dev list and someone that can merge the fixes should pick it up. Again, local testing of the fix on a branch will ensure it's speedy merging.

cheers,
Steve




On 13/05/2011, at 9:00 PM, Paul Mungai wrote:

> Hi,
> 
> Having visited the release guidelines in http://bit.ly/mE51Bc . I need some clarification.
> 
> If a bug is found on one of the tools in a release , say 2.8.0. What is the procedure, assuming one is not the branch owner.
> 
> -- 
> Regards,
> Paul Mungai
> 
> Skype: pwando
> Twitter: pwando
> Facebook: paulwando
> Blog: http://pmungai.wordpress.com
> Flickr: http://bit.ly/b84lip
> 
> "Ability is what youre capable of doing. Motivation determines what you do. Attitude determines how well you do it" By Lou Holtz, Notre Dame Football Coach
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110513/ef34dc72/attachment.html