[Deploying Sakai] [Building Sakai] Suggestions: Sakai change control list
Warwick Chapman
warwickchapman at gmail.com
Tue Jul 13 05:29:36 PDT 2010
Nope, sounds very sensible.
-- Warwick Bruce Chapman | +27 83 7797 094 | http://warwickchapman.com
On Sat, Jul 10, 2010 at 3:04 PM, David Horwitz <david.horwitz at uct.ac.za>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
> _______________________________________________
> 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/production/attachments/20100713/31f0e860/attachment.html
More information about the production
mailing list