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

[Ian Boston]

Hi,

I dont think it makes sense to have or to expect Nakamura to post.... that would make it a high volume list as we are still in very rapid development.
The best place to see changes to protocols is by watching the documentation [1], as we document everything when we do it (well thats the aim, 80% is probably closer to the mark)

Makes perfect sense for those in production, but sakai-dev appears to be low traffic now so that might work just as well. all it really needs is some tag [API CHANGE] ?

Ian

1 http://bit.ly/acAkK1

On 10 Jul 2010, at 14:04, 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
> _______________________________________________
> 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"