[Systers-dev] Release Process - Please Read

[Yian Shang]

I got a 'permission denied' error when pushing to
lp:~systers-dev/systers/archive/your-specific-project,
so I ended up pushing to lp:~systers-dev/systers/archive-ui instead.

Also, on the topic of testing, is there a test mbox file (I think I saw one
before, just can't remember where) that I can run trials on? I've been
generating my own, but I'm afraid they're not quite comprehensive enough.

Thanks,
Yian

On Mon, Jun 28, 2010 at 11:28 PM, Jennifer Redman <jenred at gmail.com> wrote:

> 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
>
>
> To unsubscribe from this conversation, send email to <
> systers-dev+release+unsubscribe at systers.org<systers-dev%2Brelease%2Bunsubscribe at systers.org>>
> or visit <
> http://systers.org/mailman/options/systers-dev?override=137&preference=0>
> To contribute to this conversation, use your mailer's reply-all or
> reply-group command or send your message to
> systers-dev+release at systers.org <systers-dev%2Brelease at systers.org>
> To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
> >
> To unsubscribe entirely from systers-dev, send email to <
> systers-dev-request at systers.org> with subject unsubscribe.
>