[ckan-dev] How we use trac

[Ian Murray]

On 25 June 2012 14:37, Sean Hammond <sean.hammond at okfn.org> wrote:

> > On 25 Jun 2012, at 13:44, Ian Murray wrote:
> > > I think this would best fit into the status workflow:
> > >
> > > new -> accepted -> assigned -> in development [-> awaiting merge] ->
> > > closed
> >
> > Actually I'd prefer to swap accepted and assigned, someone can assign
> > the bug to me, but until I accept it, I'm not working on it.
>
> Exactly
>

Ok, that's cool.  I hadn't realised it was not linear, and could be
re-ordered like that.

I'm happy to use that convention to indicate something I'm working on.


>
> > > Personally, I'm more in favour of "awaiting merge" being a status than
> a priority.
> >
> > Does Trac allow us to add statuses? If so, I'm happy with that too.
>
> It can be customised, you have to ssh into the trac server and edit the
> ini file, I was planning to do this anyway in order to install some
> plugins, but was waiting until after the ever-imminent upgrade
>
> http://trac.edgewall.org/wiki/TracWorkflow
>
> I kind of think that if we can get by with the default workflow we
> should, less customisation is going to be easier to understand and
> maintain going forward (running a highly tricked-out trac instance with
> loads of plugins and custom configurations is probably not a good idea)
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20120625/711d33a1/attachment-0001.html>