Re: [babel-dev] Babel release process for Git

[Denis Roy <denis.roy@xxxxxxxxxxx>]

The babel staging area is now pulling from Git HEAD:
http://babel.eclipse.org/staging

I still need to figure out how we'll release.  Kit, I've compiled some notes on tagging -- you must tag your local repo, then push the tag.  Please try these steps out for tagging -- don't worry, the live code won't be affected.

http://wiki.eclipse.org/Babel_/_Server_Tool_Development_Process#Release_process

I'm thinking that since the babel staging area is essentially a "git clone" with the HEAD stream checked out, upon release, we could:

a) tag
b) let the staging site pull the new tag
c) as part of our deployment, we have the staging area checkout the tag we just created.  This will allow us to test the tagged version
d) the deployment process would then copy all the staging area's files to the production area.
e) staging then returns to the HEAD stream

This way, we don't necessarily maintain two entire git clones (one for staging and one for production).

I'll be focusing my energy on that next week to see how it goes.  I'll keep you informed.  Kit, in the meanwhile, you can start merging your changes to the Git repo and testing them on staging.  I'll have this figured out soon.

Denis

On 11/01/2012 09:20 AM, Denis Roy wrote:

Hi Kit,

I'll be working on Babel today to kickstart the release process in Git.  I'll put up docs and post up when I'm done.

Thanks,

Denis

On 10/23/2012 12:08 AM, Kit Lo wrote:

Denis,

Now that we have migrated the Babel repositories to Git. Could you recommend the Babel release process? Is there an equivalent of tagging the code with a release tag R_x_YYYYMMDDHHMM in Git?