[Systers-dev] Release Process - Please Read

[Jennifer Redman]

So I think that I've mentioned the release process to individuals but have
not sent out the information to everyone.

Syster servers:

Production - artemis.systers.org - this is where the main
systers.orgmailing lists run
Staging/Testing - abiwt.org
Development - dev.systers.org - this is where we are going to test
experimental branches - and everyone is going to be given shell-access.

First, every GSoC student needs to be a member of the systers-dev group on
launchpad.  Right now just Jaideep, Vidya, and Anna are members.  Please
request to join the group and I'll approve you asap.

Next everyone needs to create a branch under lp:~systers-dev with your code
you are developing this summer.  Make sure you use a name that is
representative of the project, and mark the branch experimental.

In the case of the archives project I recommend doing something like:
lp:~syster-dev/systers/archive/your-specific-project.

You should be committing locally and pushing to launchpad on a regular
basis.

If you need to pull the stable branch use:  lp:systers (stable - running on
production - artemis.systers.org)
If you need to pull the development branch use:
lp:~systers-dev/systers/development (if we are in a testing cycle - like we
are now - this is what is running on abiwt.org)

Right now the release process happens like this:

1) - Bug fixes are made and checked into the individual's branch
1.5) Sometimes bug fixes are made on abiwt.org and committed to the
development branch via that system (step 2 is then not necessary)
2) - Jen merges the bug fix branch with development
3) - Jen pulls the development branch on to abiwt.org so testing can begin.
4) - Upon successful completion of the test-cycle, Jen merges the
development branch with the stable branch
5) - Maintenance window is scheduled for production (artemis.systers.org)
and the code is updated via a update against the newly updated stable
branch.

The above process needs to change - which is why we have a release
management project this summer -- but for now this is how things work, and
will work until after mid-terms.

If you have an existing branch on lauchpad -- you should be able to clone it
under systers-dev no problem.  I think it's fine to keep copies in both
places -- but in order to do code reviews and merges -- we need to have a
copy of your branch under systers-dev.

(See "Release Managment" here -
http://systers.org/systers-dev/doku.php/development_process.)

Let me know if you have any questions,

Jen