[pygr-notify] [pygr] r252 committed - XML-RPC server should always be updated when a release happens, someti...

codesite-noreply at google.com codesite-noreply at google.com
Tue Aug 4 18:33:07 PDT 2009


Revision: 252
Author: marecki
Date: Tue Aug  4 18:31:55 2009
Log: XML-RPC server should always be updated when a release happens,  
sometimes during beta-testing as well.
http://code.google.com/p/pygr/source/detail?r=252

Modified:
  /wiki/ReleaseProcedure.wiki

=======================================
--- /wiki/ReleaseProcedure.wiki	Mon Apr 20 15:13:37 2009
+++ /wiki/ReleaseProcedure.wiki	Tue Aug  4 18:31:55 2009
@@ -24,7 +24,7 @@

  === Beta-testing ===

-Starts with: tagging the Git master with a "beta" tag (with appropriate  
number), creation of a "beta" package of Pygr (tarball at the least, other  
formats as wanted/needed)
+Starts with: tagging the Git master with a "beta" tag (with appropriate  
number), creation of a "beta" package of Pygr (tarball at the least, other  
formats as wanted/needed). If the UCLA XML-RPC server is based on Git code  
and not the last release, it should be switched to the new beta code at  
this point as well.

  Allowed commits in Git master: bug fixes and documentation updates only

@@ -39,4 +39,4 @@

  Allowed commits in Git master: none

-Ends with: packages (all agreed-upon formats) created and published on the  
Web site
+Ends with: packages (all agreed-upon formats) created and published on the  
Web site, UCLA XML-RPC server updated to use current release code.



More information about the pygr-notify mailing list