oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

Hi All,

The OSHIP trunk has now been migrated to Grok 1.0b2.
There are major changes in directory structures and to the eggs
required.  So your need to do a complete new installation.

**IF** you were doing a code-review and have local changes that you did
not post to a branch.  Contact me directly and I will help you migrate
your code.  Just rename your current directory oship_backup or something
like that and create a new virtual environment with Python2.5 (we still
are not quite 2.6 compatible on all platforms yet).

In order to simplify how OSHIP developers correct bugs and and
eventually add features to OSHIP I have made some changes to the
Launchpad site as well as the oship-dev team.  

I will be updating the FAQs and sending more information later.  But the
basics now are that every developer will be getting a copy of the trunk
code bzr branch lp:oship  They will make their changes on this branch
and push them back to this branch.  So you will also need to learn how
to use the bzr update command to be sure you stay in sync with the
latest copy of the trunk.  BUT! you do not need to register your own
branch anymore.  This seemed to cause a lot of confusion with new
comers.  When the trunk is at various points of stability I will pull
off branches and create distributions; i.e. 1.0b1 

So, now all any of you have to worry about is the trunk.  Fix
bugs!!!!!! :-)  I'll be adding lots of bug reports.  Select some you
want to work on and self assign them.

More news soon.

Cheers,
Tim



-- 
***************************************************************
Timothy Cook, MSc

LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == (upon request)
Academic.Edu Profile: http://uff.academia.edu/TimothyCook

You may get my Public GPG key from  popular keyservers or    
from this link http://timothywayne.cook.googlepages.com/home

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