Should the 2.1 milestone be dropped or changed to 2.2?

Now that LyX 2.1 is coming up, many tickets are being dealt with. For these tickets, if they aren't likely to make it into 2.1, the milestone is being dropped. Is this what's normally done? I was expecting the milestone to be changed to 2.2. Is it correct that the tickets with milestone 2.1 that

Re: Should the 2.1 milestone be dropped or changed to 2.2?

On 05/13/2013 10:17 AM, Scott Kostyshak wrote: Now that LyX 2.1 is coming up, many tickets are being dealt with. For these tickets, if they aren't likely to make it into 2.1, the milestone is being dropped. Is this what's normally done? I was expecting the milestone to be changed to 2.2. Is it

Re: Should the 2.1 milestone be dropped or changed to 2.2?

On Mon, May 13, 2013 at 4:25 PM, Richard Heck rgh...@lyx.org wrote: I think that's the idea: that we re-think all the targeted bugs and decide if they really should be targeted. I've reset milestones for a few already. I think so, too. This basically means that if a devel works on the feature

Re: Should the 2.1 milestone be dropped or changed to 2.2?

Scott Kostyshak wrote: Is it correct that the tickets with milestone 2.1 that don't make it into to 2.1 will not be treated like tickets with no milestone? It depends, many enhacenment bugs are there for years and no one is going to touch them. Milestone has some meaning if there is reason to

Re: Should the 2.1 milestone be dropped or changed to 2.2?

On Mon, May 13, 2013 at 10:25 AM, Richard Heck rgh...@lyx.org wrote: On 05/13/2013 10:17 AM, Scott Kostyshak wrote: Perhaps this is a good thing. This would force us to think about all of the milestones of all unmarked tickets. There are probably some old tickets that are being ignored that

Re: Should the 2.1 milestone be dropped or changed to 2.2?

On Mon, May 13, 2013 at 1:52 PM, Pavel Sanda sa...@lyx.org wrote: Scott Kostyshak wrote: Is it correct that the tickets with milestone 2.1 that don't make it into to 2.1 will not be treated like tickets with no milestone? It depends, many enhacenment bugs are there for years and no one is

Re: Should the 2.1 milestone be dropped or changed to 2.2?

Scott Kostyshak wrote: I think the milestone should also be set if someone *should* be working on it. There are some bugs that I report/modify that are not I'm afraid that number of bugs that we consider *someone else* should really do it is already 4*zillion ;) P

Re: Should the 2.1 milestone be dropped or changed to 2.2?

On Mon, May 13, 2013 at 2:10 PM, Pavel Sanda sa...@lyx.org wrote: Scott Kostyshak wrote: I think the milestone should also be set if someone *should* be working on it. There are some bugs that I report/modify that are not I'm afraid that number of bugs that we consider *someone else* should

Re: Should the 2.1 milestone be dropped or changed to 2.2?

On Mon, May 13, 2013 at 8:35 PM, Scott Kostyshak skost...@lyx.org wrote: But there should be some way to specify urgency. 'Priority' seems determined by other variables so is not used for this. I think 'Severity' serves this purpose. High severity usually pertains to problematic bugs (not

Re: Should the 2.1 milestone be dropped or changed to 2.2?

Op 13 mei 2013 20:39 schreef Vincent van Ravesteijn v...@lyx.org het volgende: Op 13 mei 2013 16:18 schreef Scott Kostyshak skost...@lyx.org het volgende: Now that LyX 2.1 is coming up, many tickets are being dealt with. For these tickets, if they aren't likely to make it into 2.1, the

Re: Should the 2.1 milestone be dropped or changed to 2.2?

Liviu Andronic wrote: I think 'Severity' serves this purpose. High severity usually pertains to problematic bugs (not enhancements); these include crashes, data loss, etc. Yes, I will add it to the FAQ if it's not there yet. P

Re: Should the 2.1 milestone be dropped or changed to 2.2?

Scott Kostyshak wrote: Anyways, I won't fight this anymore, except that however milestone is used, I think it should be used the same by everyone. If there's inconsistent treatment across time (e.g. *if* in transition from 2.0 to 2.1 all tickets with milestone 2.0 are changed to 2.1 but in 2.1

Should the 2.1 milestone be dropped or changed to 2.2?

Now that LyX 2.1 is coming up, many tickets are being dealt with. For these tickets, if they aren't likely to make it into 2.1, the milestone is being dropped. Is this what's normally done? I was expecting the milestone to be changed to 2.2. Is it correct that the tickets with milestone 2.1 that

Re: Should the 2.1 milestone be dropped or changed to 2.2?

On 05/13/2013 10:17 AM, Scott Kostyshak wrote: Now that LyX 2.1 is coming up, many tickets are being dealt with. For these tickets, if they aren't likely to make it into 2.1, the milestone is being dropped. Is this what's normally done? I was expecting the milestone to be changed to 2.2. Is it

Re: Should the 2.1 milestone be dropped or changed to 2.2?

On Mon, May 13, 2013 at 4:25 PM, Richard Heck wrote: > I think that's the idea: that we re-think all the targeted bugs and decide > if they really should be targeted. I've reset milestones for a few already. > I think so, too. This basically means that if a devel works on the

Re: Should the 2.1 milestone be dropped or changed to 2.2?

Scott Kostyshak wrote: > Is it correct that the tickets with milestone 2.1 that don't make it > into to 2.1 will not be treated like tickets with no milestone? It depends, many enhacenment bugs are there for years and no one is going to touch them. Milestone has some meaning if there is reason

Re: Should the 2.1 milestone be dropped or changed to 2.2?

On Mon, May 13, 2013 at 10:25 AM, Richard Heck wrote: > On 05/13/2013 10:17 AM, Scott Kostyshak wrote: >> Perhaps this is a good thing. This would force us to think about all >> of the milestones of all unmarked tickets. There are probably some old >> tickets that are being

Re: Should the 2.1 milestone be dropped or changed to 2.2?

On Mon, May 13, 2013 at 1:52 PM, Pavel Sanda wrote: > Scott Kostyshak wrote: >> Is it correct that the tickets with milestone 2.1 that don't make it >> into to 2.1 will not be treated like tickets with no milestone? > > It depends, many enhacenment bugs are there for years and no

Re: Should the 2.1 milestone be dropped or changed to 2.2?

Scott Kostyshak wrote: > I think the milestone should also be set if someone *should* be > working on it. There are some bugs that I report/modify that are not I'm afraid that number of bugs that we consider *someone else* should really do it is already 4*zillion ;) P

Re: Should the 2.1 milestone be dropped or changed to 2.2?

On Mon, May 13, 2013 at 2:10 PM, Pavel Sanda wrote: > Scott Kostyshak wrote: >> I think the milestone should also be set if someone *should* be >> working on it. There are some bugs that I report/modify that are not > > I'm afraid that number of bugs that we consider *someone else*

Re: Should the 2.1 milestone be dropped or changed to 2.2?

On Mon, May 13, 2013 at 8:35 PM, Scott Kostyshak wrote: > But there should be some way to specify urgency. 'Priority' seems > determined by other variables so is not used for this. > I think 'Severity' serves this purpose. High severity usually pertains to problematic bugs (not

Re: Should the 2.1 milestone be dropped or changed to 2.2?

Op 13 mei 2013 20:39 schreef "Vincent van Ravesteijn" het volgende: > > Op 13 mei 2013 16:18 schreef "Scott Kostyshak" het > volgende: > > > > Now that LyX 2.1 is coming up, many tickets are being dealt with. For > > these tickets, if they aren't likely to make

Re: Should the 2.1 milestone be dropped or changed to 2.2?

Liviu Andronic wrote: > I think 'Severity' serves this purpose. High severity usually pertains > to problematic bugs (not enhancements); these include crashes, data > loss, etc. Yes, I will add it to the FAQ if it's not there yet. P

Re: Should the 2.1 milestone be dropped or changed to 2.2?

Scott Kostyshak wrote: > Anyways, I won't fight this anymore, except that however milestone is > used, I think it should be used the same by everyone. If there's > inconsistent treatment across time (e.g. *if* in transition from 2.0 > to 2.1 all tickets with milestone 2.0 are changed to 2.1 but in