> From: [email protected] [mailto:simal- > [email protected]] On Behalf Of Ross Gardler > Sent: 08 July 2010 15:11 > To: [email protected] > Subject: Re: [simal] r1916 committed - Added link to the SigningReleases > page. > > No need to vote on user list. They can join the dev list if they care. > Having it in two places means it is more difficult to count and discussions > may get split across lists. > > Would be good to send notification of the vote to user list though. >
Thanks for clearing this up, the releaseManagement page was contradicting itself and I chose the other solution. :) Now changed to reflect what you're saying. Sander > Sent from my mobile device. > > On 8 Jul 2010, at 14:32, [email protected] wrote: > > > Revision: 1916 > > Author: [email protected] > > Date: Thu Jul 8 06:32:08 2010 > > Log: Added link to the SigningReleases page. > > http://code.google.com/p/simal/source/detail?r=1916 > > > > Modified: > > /wiki/ReleaseManagement.wiki > > > > ======================================= > > --- /wiki/ReleaseManagement.wiki Fri Jan 8 00:42:27 2010 > > +++ /wiki/ReleaseManagement.wiki Thu Jul 8 06:32:08 2010 > > @@ -156,7 +156,7 @@ > > > > When no (more) critical errors are discovered on the last release > candidate during the testing phase we can now proceed with getting approval > for the release. > > > > -A vote on the release is called on the contributor mailing list. > > +A vote on the release is called on the contributor and user mailing > list. > > > > Assuming that the vote passes we can proceed. If it does not pass the > reason(s) for the negative votes must be addressed. > > > > @@ -164,7 +164,7 @@ > > > > The final binary release is created on the release branch. The only > difference between the final release and the last release candidate is the > version number. > > > > -*TODO:* The process on signing the release still has to be worked out. > See [http://code.google.com/p/simal/issues/detail?id=262 Issue 262]. > > +The process on signing the release is described in SigningReleases. > > > > == Ensure the demo server is running the latest release == > > > > -- > > You received this message because you are subscribed to the Google Groups > "Simal Commits" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to simal- > [email protected]. > > For more options, visit this group at > http://groups.google.com/group/simal-commits?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Simal Commits" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to simal- > [email protected]. > For more options, visit this group at http://groups.google.com/group/simal- > commits?hl=en. -- You received this message because you are subscribed to the Google Groups "Simal Commits" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/simal-commits?hl=en.
