Issue356

Title Maintain tracker modifications as Mercurial patch Queues
Priority wish Status resolved
Superseder Nosy List ezio.melotti, techtonik
Assigned To ezio.melotti Topics

Created on 2010-10-29.11:02:27 by techtonik, last changed 2012-07-29.04:42:26 by ezio.melotti.

Messages
msg1839 (view) Author: techtonik Date: 2010-10-29.11:02:26
To make maintenance of bug trackers easier and encourage upstream collaborations, I propose to do tracker maintenance using Mercurial patch Queues:

1. Official RoundUp repository is mirrored to our local Mercurial ones.
2. No commits are made into mirror.
3. Patches are instead stacked into MQ repositories - one for each instance.
4. Instances are synchronized to new Roundup version using the following process
  4.1. New changes are pulled into local clone
  4.2. MQ patches are applies (and fixed if needed)
  4.3. Tests are run
  4.4. Repository is exported to production

Once proven, this can be extended to MoinMoin maintenance as well.

[1] http://psf.upfronthosting.co.za/roundup/meta/issue278
msg2564 (view) Author: ezio.melotti Date: 2012-07-29.04:42:26
This is now done with a separate branch on http://hg.python.org/tracker/roundup/.
History
Date User Action Args
2012-07-29 04:42:26ezio.melottisetstatus: unread -> resolved
assignedto: ezio.melotti
messages: + msg2564
nosy: + ezio.melotti
2010-10-29 11:02:27techtonikcreate