[Deploying Sakai] [Management] Suggestions: Sakai change control list

[David Haines]

+1 

It would be good to have a low volume list only for changes that will adversely impact existing core code.  Would the list include a call for discussion of potential changes or just announcement of changes that have been done and committed?  

- Dave

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




On Jul 10, 2010, at 9:04 AM, David Horwitz wrote:

>  Hi all,
> 
> This was a suggestion I made at the closing project planing meeting in 
> Denver after chatting to Rutgers and their upgrade experience:
> 
> 
> We establish a change control list for Sakai. This would be a low volume 
> alert list to warn adopters of potentially disruptive changes.  The list 
> would be public read but have limited posting rights. Initially I would 
> suggest the following have posting rights:
> 
> - Maintenance Team
> - Kernel Team
> - Nakamura team
> - Core project teams.
> 
> The sort of things I envision being sent to the list include:
> - Changes to public API's
> - Changes in name or default for properties
> - Changes in maven group or artifact names
> 
> 
> Any objections to asking for this list to be created?
> 
> Regards
> 
> David
> _______________________________________________
> management mailing list
> management at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/management
> 
> TO UNSUBSCRIBE: send email to management-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20100714/de04aac9/attachment.html