Trac: fixedinmaster, fixedinstable

[Vincent van Ravesteijn]

Hi all,

I've implement the fixedinmaster and fixedinstable states in trac.

The following ticket workflow is now possible:

new -> fixedinmaster -> fixedinmasterandstable -> closed
new -> fixedinstable -> fixedinmasterandstable -> closed
new -> fixedinmaster -> closed
new -> fixedinstable -> closed

I've changed bug #7944 accordingly: http://www.lyx.org/trac/ticket/7944

Also, the roadmap has been adapted. Now, all bugs that have a fixedin*
status, are marked as fixed, and the percentage for the milestone is
computed taking this into account.

http://www.lyx.org/trac/roadmap

Next steps are:
- update all other bugs that now have fixedintrunk and/or fixedinbranch
keywords,
- remove the fixedintrunk, fixedinbranch keywords,
- update the BugTrackerHome page.

Any comments before I proceed ?

Vincent

[Richard Heck]

Post by Vincent van Ravesteijn
Hi all,
I've implement the fixedinmaster and fixedinstable states in trac.
new -> fixedinmaster -> fixedinmasterandstable -> closed
new -> fixedinstable -> fixedinmasterandstable -> closed
new -> fixedinmaster -> closed
new -> fixedinstable -> closed
I've changed bug #7944 accordingly: http://www.lyx.org/trac/ticket/7944
Also, the roadmap has been adapted. Now, all bugs that have a fixedin*
status, are marked as fixed, and the percentage for the milestone is
computed taking this into account.
http://www.lyx.org/trac/roadmap
- update all other bugs that now have fixedintrunk and/or
fixedinbranch keywords,

Most of those will be closed with the release of 2.1.0 and 2.0.8, except
(I think) for the ones with a 2.1.1 milestone.

Post by Vincent van Ravesteijn
- remove the fixedintrunk, fixedinbranch keywords,
- update the BugTrackerHome page.
Any comments before I proceed ?

Can we make it "fixedinboth" or something like that instead of
"fixedinmasterandstable". The latter is just really long.

Can you remind me why we need "fixedinmasterandstable" anyway? and not
just "fixedinmaster fixedinstable", as we had before? I know we
discussed this....

Richard

[Vincent van Ravesteijn]

Post by Vincent van Ravesteijn
Hi all,
I've implement the fixedinmaster and fixedinstable states in trac.
new -> fixedinmaster -> fixedinmasterandstable -> closed
new -> fixedinstable -> fixedinmasterandstable -> closed
new -> fixedinmaster -> closed
new -> fixedinstable -> closed
I've changed bug #7944 accordingly: http://www.lyx.org/trac/ticket/7944
Also, the roadmap has been adapted. Now, all bugs that have a fixedin*
status, are marked as fixed, and the percentage for the milestone is
computed taking this into account.
http://www.lyx.org/trac/roadmap
- update all other bugs that now have fixedintrunk and/or fixedinbranch
keywords,

Most of those will be closed with the release of 2.1.0 and 2.0.8, except (I
think) for the ones with a 2.1.1 milestone.

Yes, I was not going to change those with milestone 2.1.0 and 2.0.8.

Post by Vincent van Ravesteijn
- remove the fixedintrunk, fixedinbranch keywords,
- update the BugTrackerHome page.
Any comments before I proceed ?

Can we make it "fixedinboth" or something like that instead of
"fixedinmasterandstable". The latter is just really long.

Well, yes, but you don't have to type this. Switch between statuses is
done by choosing a radiobutton. So, I personally don't have a problem
with the length.

Can you remind me why we need "fixedinmasterandstable" anyway? and not just
"fixedinmaster fixedinstable", as we had before? I know we discussed
this....

I'm not sure what you exactly mean, but:
- a ticket cannot be in multiple statuses,
- a status probably can't contain a space.

Richard

Vincent

[Jean-Marc Lasgouttes]

Post by Vincent van Ravesteijn

Can you remind me why we need "fixedinmasterandstable" anyway? and not just
"fixedinmaster fixedinstable", as we had before? I know we discussed
this....

- a ticket cannot be in multiple statuses,
- a status probably can't contain a space.

What about 'fixed' ?

JMarc

[Vincent van Ravesteijn]

On Tue, Apr 15, 2014 at 10:09 AM, Jean-Marc Lasgouttes

Post by Jean-Marc Lasgouttes

Post by Vincent van Ravesteijn

Can you remind me why we need "fixedinmasterandstable" anyway? and not just
"fixedinmaster fixedinstable", as we had before? I know we discussed
this....

- a ticket cannot be in multiple statuses,
- a status probably can't contain a space.

What about 'fixed' ?
JMarc

Yes, ok, I will do that.

Vincent

[Benjamin Piwowarski]

Hi,

and what about a new issue tracking system - one that would handle multiple versions and integrate nicely with git? It seems that lyx project is hitting the trac limits all the time and from what I have seen, these issues are not solved. I would be OK to help with migration on that level - I played a bit with bug genie for instance and it seems to handle this quite well (at least it handles different versions with different statuses) - see e.g. http://www.thebuggenie.com/features
 
benjamin

Post by Vincent van Ravesteijn

Can you remind me why we need "fixedinmasterandstable" anyway? and not just
"fixedinmaster fixedinstable", as we had before? I know we discussed
this....

- a ticket cannot be in multiple statuses,
- a status probably can't contain a space.

What about 'fixed' ?

JMarc

[Richard Heck]

Post by Vincent van Ravesteijn

Post by Richard Heck

Post by Vincent van Ravesteijn
- remove the fixedintrunk, fixedinbranch keywords,
- update the BugTrackerHome page.
Any comments before I proceed ?

Can we make it "fixedinboth" or something like that instead of
"fixedinmasterandstable". The latter is just really long.

Well, yes, but you don't have to type this. Switch between statuses is
done by choosing a radiobutton. So, I personally don't have a problem
with the length.

Post by Richard Heck
Can you remind me why we need "fixedinmasterandstable" anyway? and not just
"fixedinmaster fixedinstable", as we had before? I know we discussed
this....

- a ticket cannot be in multiple statuses,
- a status probably can't contain a space.

Sorry, I forgot these were statuses now.

rh

[Tommaso Cucinotta]

Post by Richard Heck
Can you remind me why we need "fixedinmasterandstable" anyway? and
not just "fixedinmaster fixedinstable", as we had before? I know we
discussed this....

And can anyone please remind everyone else what master and stable exactly are?

Just asking, as due to the current long permanence in the new 2.x-staging branches,
so I confess I'm a bit lost here with how many branches are needed during release
finalizations. Better, would be to note this down on the devel wiki somewhere.

Thanks,

T.