oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

On Sat, 2009-11-14 at 15:24 +0100, Roger Erens wrote:

> OK, 'release' was maybe too big a word.
> At first, I want to see what changes are necessary in the bzr
> repository to achieve Grok1.1/ZTK/Python2.6 dependency.
> Especially, since I'm no buildout-guru, the buildout.cfg and setup.py
> and bootstrap.py files.

Okay.  Maybe you are looking more for:  What did I do to be sure we
moved up to Grok 1.0?  

I setup a new branch on my local machine to to do testing.

1.  I installed the new grokproject and created a sample application.

2.  I reviewed setup.py for any updates.

3.  I already knew that there were directory modifications in buildout
because I kept track of what was going on in the mailing lists so I made
those changes in the appropriate places (this was the trickiest part but
shouldn't ever happen again).

4.  I made sure that buildout.cfg pointed to the 1.0 tar ball instead of
the 1.0a

5.  Though I did review it, I took the new versions.cfg; wholesale and
replaced the old one in OSHIP. 

6.  When all seemed to be working okay.  I created a new test branch on
Launchpad.  Pushed to it.  Took a deep breath, deleted all of my shared
eggs.  Branched the test branch back down, ran bootstrap.py,
bin/buildout then went through all the demos again.  Just to be sure I
could go through a complete install as if I had no existing prereqs
other than virtualenv, etc.  

7.  When everything worked.  I merged it to the trunk and declared it
upgraded to Grok 1.0

Cheers,
Tim

PS.  You can always see our progress to OSHIP 1.0 by checking the
dependency graphic associated with the Blueprint:
https://blueprints.launchpad.net/oship/+spec/oship-release-1.0

Attachment: signature.asc
Description: This is a digitally signed message part