[SciPy-dev] Trac-ing backports
Charles R Harris
Thu Jun 4 20:26:57 CDT 2009
On Thu, Jun 4, 2009 at 3:00 PM, Pauli Virtanen <email@example.com> wrote:
> I noticed that keeping track of bugs to backport is a bit painful. Also
> Trac isn't currently too helpful about this.
Welcome to the club of pain.
> So, how should we deal with backports within Trac:
> a) For each bug you think could be useful to backport, before closing the
> ticket, file a new "Backport #xxx to 0.y.z" ticket. Easy to forget,
> though, and a bit nasty with Numpy with its 1.0.x, 1.1.x, 1.2.x, 1.3.x,
> b) Add a custom field "Branches" that contains some custom format, such as
> "-1.3.x" before and "+1.3.x" after backporting. Add corresponding
> queries to Trac's roadmap.
c) Limit bug fix releases ;)
If there was some easy way to generate backport tickets (tasks) by simply
marking current tickets that might help.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Scipy-dev