managing snapshots

[Rick Gigger]

Mark,

How would you like to manage the process of regularly validating a
snapshot, making a tarball and uploading it to the google code site?
We should probably do that ever 3 or 4 months. Right now the current
tar ball is almost a year old. We don't want anyone using that.

Rick

[Mark Suman]

That sounds fine to me, I can handle that.  To make sure I've got it right:

1. Make an export of the zoop repo
2. Tar it up
3. Stick it on the website

Is that it?  I'll make a new tarball after you and I meet and I get up to speed on the new additions.

Mark

[Rick Gigger]

Well, the first step is to make sure that none of the examples are broken but that doesn't have to be you.

Then you need to update the api docs to reflect all of the current code.  I'm not sure if we want this all commited to the repository or if we just wanted it updated in the tar balls.

After that it's just as you list below.

Rick

[Mark Suman]

I'll try and take on the responsibility of testing all the examples.  If it's too much, I'll reach out for some help.  I can generate the API doc, too.  I'm using PHPDocumentor on my current project as well.  Do you have a specific configuration command you like to run for it or would you like me to just to make one up that looks nice?

Mark

[Rick Gigger]

This is all I'm using right now.  Feel free to do anything you like with it.

[Rick Gigger]

Oops, I forgot to paste this in my last email:

http://zoop.googlecode.com/svn/trunk/update_api_docs.sh

That script has the command we are currently using.  If you do something different just update that file so anyone can do it in a consistent way.

Rick

On Apr 14, 2008, at 9:25 PM, Mark Suman wrote:

[Mark Suman]

Sounds good.