search

eftsung / pygr

Automatically exported from code.google.com/p/pygr
0 stars 0 forks source link

Write a release procedure #32

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
as Titus suggested, we should write a SOP for producing the final
package(s) of any release.

Original issue reported on code.google.com by cjlee...@gmail.com on 11 Sep 2008 at 3:49

GoogleCodeExporter commented 8 years ago 
Side note: if we use package-building capabilities of setuptools it will 
simplify 
the release procedure. This will require updating setup.cfg (right now it only 
contains some outdated and incomplete specs for building RPMs) as well as 
removing 
package-building data from setup.py (this has already been done as a part of 
Istvan's rewrite of that script, to be merged with the master soon).

Original comment by mare...@gmail.com on 4 Mar 2009 at 12:40

GoogleCodeExporter commented 8 years ago 
Marek, I propose you do this...

Original comment by cjlee...@gmail.com on 8 Apr 2009 at 1:52

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
See the relevant page on Pygr Wiki: ReleaseProcedure (work in progress)

Original comment by mare...@gmail.com on 15 Apr 2009 at 1:06

GoogleCodeExporter commented 8 years ago 
Whoops, forgot to update this earlier... The procedure can now be considered 
complete.

Original comment by mare...@gmail.com on 13 May 2009 at 2:15