[sakai2-tcc] [maint] Maintenance Branches: Enhancement vs Bug Merges

[David Haines]

That's an appropriate concern but I suspect the effect of making the maintenance branches more active would be to increase the number of people willing to work on getting bug fixes into code.  If someone has good reason to think they can get an appropriate change into Sakai quickly (and so won't then get stuck maintaining their own maintenance branch until the next major release) then they are more likely to be able to justify the work to put in the work to test and integrate the change back into the Sakai source tree.

- Dave 

David Haines
CTools Developer
Digital Media Commons
University of Michigan 
dlhaines at umich.edu



On Jan 5, 2011, at 9:53 AM, Seth Theriault wrote:

> Anthony Whyte wrote:
> 
>> Moreover, encouraging schools to remain on older 
>> branches because we might sprinkle them occasionally with new 
>> stuff while at the same time neglecting to merge fixes into 
>> these branches in a timely manner is not, under current 
>> conditions, in the Community interest (have a look in Jira at 
>> the current backlog of 2.6.x and 2.7.x closed/resolved issues 
>> that need merging).
> 
> I think this is an important point. If we don't have the time and 
> people to manage bug fixes, how do we have the time and people 
> for features/enhancements if bug fixes are supposedly a priority?
> 
> Seth
> 
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20110105/eeaf4f91/attachment.html