You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Sylvain Laurent <sy...@m4x.org> on 2010/10/23 00:11:01 UTC
bugzilla question : bugs fixed in trunk but not yet in tc6
How can you create a filter for bugs that are fixed in trunk, proposed to be fixed in tomcat 6, and waiting to be backported ? Do you use some special bug attribute ?
Sylvain
PS : Why not use JIRA ? It has many advantages over this aging bugzilla...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: bugzilla question : bugs fixed in trunk but not yet in tc6
Posted by Mark Thomas <ma...@apache.org>.
On 23/10/2010 01:15, Josh Gooding wrote:
> They could be comfortable with Bugzilla too. I see JIRA has an open source
> license. (back pedal back pedal!!!)
Yep, and the ASF has a a free enterprise license for it too.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: bugzilla question : bugs fixed in trunk but not yet in tc6
Posted by Sylvain Laurent <sy...@m4x.org>.
JIRA is available for Apache projects : http://issues.apache.org/jira/
On 23 oct. 2010, at 02:15, Josh Gooding wrote:
> They could be comfortable with Bugzilla too. I see JIRA has an open source
> license. (back pedal back pedal!!!)
>
> On Fri, Oct 22, 2010 at 8:10 PM, Josh Gooding <jo...@gmail.com>wrote:
>
>> Not to step on anyones toes, but JIRA costs serious $$ after the initial 10
>> users. It gets expensive fast. Trac is good too though. I set up an
>> awesome Trac system at work.
>>
>> - Josh
>>
>>
>> On Fri, Oct 22, 2010 at 6:11 PM, Sylvain Laurent <sy...@m4x.org>wrote:
>>
>>> How can you create a filter for bugs that are fixed in trunk, proposed to
>>> be fixed in tomcat 6, and waiting to be backported ? Do you use some special
>>> bug attribute ?
>>>
>>> Sylvain
>>>
>>> PS : Why not use JIRA ? It has many advantages over this aging bugzilla...
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: dev-help@tomcat.apache.org
>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: bugzilla question : bugs fixed in trunk but not yet in tc6
Posted by Josh Gooding <jo...@gmail.com>.
They could be comfortable with Bugzilla too. I see JIRA has an open source
license. (back pedal back pedal!!!)
On Fri, Oct 22, 2010 at 8:10 PM, Josh Gooding <jo...@gmail.com>wrote:
> Not to step on anyones toes, but JIRA costs serious $$ after the initial 10
> users. It gets expensive fast. Trac is good too though. I set up an
> awesome Trac system at work.
>
> - Josh
>
>
> On Fri, Oct 22, 2010 at 6:11 PM, Sylvain Laurent <sy...@m4x.org>wrote:
>
>> How can you create a filter for bugs that are fixed in trunk, proposed to
>> be fixed in tomcat 6, and waiting to be backported ? Do you use some special
>> bug attribute ?
>>
>> Sylvain
>>
>> PS : Why not use JIRA ? It has many advantages over this aging bugzilla...
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: dev-help@tomcat.apache.org
>>
>>
>
Re: bugzilla question : bugs fixed in trunk but not yet in tc6
Posted by Josh Gooding <jo...@gmail.com>.
Not to step on anyones toes, but JIRA costs serious $$ after the initial 10
users. It gets expensive fast. Trac is good too though. I set up an
awesome Trac system at work.
- Josh
On Fri, Oct 22, 2010 at 6:11 PM, Sylvain Laurent <sy...@m4x.org>wrote:
> How can you create a filter for bugs that are fixed in trunk, proposed to
> be fixed in tomcat 6, and waiting to be backported ? Do you use some special
> bug attribute ?
>
> Sylvain
>
> PS : Why not use JIRA ? It has many advantages over this aging bugzilla...
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
Re: bugzilla question : bugs fixed in trunk but not yet in tc6
Posted by sebb <se...@gmail.com>.
On 23 October 2010 12:05, Mark Thomas <ma...@apache.org> wrote:
> On 23/10/2010 11:40, Sylvain Laurent wrote:
>> so, we lose the information of what bug was fixed in which version for tomcat 7 ? (apart from the comments)
>
> Yes, but that was always the case with Bugzilla. You get the version it
> was reported against, not the version it was fixed in.
>
>> For instance for https://issues.apache.org/bugzilla/show_bug.cgi?id=49625 it is now marked for tomcat 6. And only the comments can tell us that it was fixed in 7.0.3 ??
>
> The primary source of that information is the changelog, not Bugzilla.
> Many years ago we used to just add a comment that it was fixed in a
> particular major version without the exact version in which it was
> fixed. We started adding the fixed version in response to a user's
> request. Personally, I don't use it that often - I use the changelog.
>
> JIRA can track this information (it can also generate changelogs) but I
> don't think it is anything the committers have felt they needed. At
> least I haven't.
>
> I'm not against switching to JIRA, but neither am I particularly for it
> either. I actually have a slight preference for Bugzilla since I prefer
> simple tools that provide the info I need rather than ones that have
> lots of bells and whistles that I don't need.
>
> The Bugzilla search interface is probably its weakest component. We are
> due an upgrade to 3.6.x which includes the results of a usability study
> which may improve this - I haven't checked yet.
IMO search is one of the weakest areas of JIRA. [The other weak area
is attachment handling - Bugzilla handles them much better.]
However, in this case, JIRA search might not be needed as one can look
for "Fix version" directly.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: bugzilla question : bugs fixed in trunk but not yet in tc6
Posted by Mark Thomas <ma...@apache.org>.
On 23/10/2010 11:40, Sylvain Laurent wrote:
> so, we lose the information of what bug was fixed in which version for tomcat 7 ? (apart from the comments)
Yes, but that was always the case with Bugzilla. You get the version it
was reported against, not the version it was fixed in.
> For instance for https://issues.apache.org/bugzilla/show_bug.cgi?id=49625 it is now marked for tomcat 6. And only the comments can tell us that it was fixed in 7.0.3 ??
The primary source of that information is the changelog, not Bugzilla.
Many years ago we used to just add a comment that it was fixed in a
particular major version without the exact version in which it was
fixed. We started adding the fixed version in response to a user's
request. Personally, I don't use it that often - I use the changelog.
JIRA can track this information (it can also generate changelogs) but I
don't think it is anything the committers have felt they needed. At
least I haven't.
I'm not against switching to JIRA, but neither am I particularly for it
either. I actually have a slight preference for Bugzilla since I prefer
simple tools that provide the info I need rather than ones that have
lots of bells and whistles that I don't need.
The Bugzilla search interface is probably its weakest component. We are
due an upgrade to 3.6.x which includes the results of a usability study
which may improve this - I haven't checked yet.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: bugzilla question : bugs fixed in trunk but not yet in tc6
Posted by Konstantin Kolinko <kn...@gmail.com>.
2010/10/23 Sylvain Laurent <sy...@m4x.org>:
> so, we lose the information of what bug was fixed in which version for tomcat 7 ? (apart from the comments)
> For instance for https://issues.apache.org/bugzilla/show_bug.cgi?id=49625 it is now marked for tomcat 6. And only the comments can tell us that it was fixed in 7.0.3 ??
>
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml
(as mentioned on
http://tomcat.apache.org/bugreport.html#Recently_fixed_issues )
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: bugzilla question : bugs fixed in trunk but not yet in tc6
Posted by Sylvain Laurent <sy...@m4x.org>.
so, we lose the information of what bug was fixed in which version for tomcat 7 ? (apart from the comments)
For instance for https://issues.apache.org/bugzilla/show_bug.cgi?id=49625 it is now marked for tomcat 6. And only the comments can tell us that it was fixed in 7.0.3 ??
Sylvain
On 23 oct. 2010, at 00:25, Konstantin Kolinko wrote:
> 2010/10/23 Sylvain Laurent <sy...@m4x.org>:
>> How can you create a filter for bugs that are fixed in trunk, proposed to be fixed in tomcat 6, and waiting to be backported ? Do you use some special bug attribute ?
>
> What do you mean?
>
> If it is already fixed in TC7, we change the product that the bug is
> assigned to: we move it to the one where it is still present: to TC6,
> then to TC5.
>
>
> Best regards,
> Konstantin Kolinko
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: bugzilla question : bugs fixed in trunk but not yet in tc6
Posted by Konstantin Kolinko <kn...@gmail.com>.
2010/10/23 Sylvain Laurent <sy...@m4x.org>:
> How can you create a filter for bugs that are fixed in trunk, proposed to be fixed in tomcat 6, and waiting to be backported ? Do you use some special bug attribute ?
What do you mean?
If it is already fixed in TC7, we change the product that the bug is
assigned to: we move it to the one where it is still present: to TC6,
then to TC5.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: bugzilla question : bugs fixed in trunk but not yet in tc6
Posted by Mark Thomas <ma...@apache.org>.
On 22/10/2010 23:11, Sylvain Laurent wrote:
> How can you create a filter for bugs that are fixed in trunk, proposed to be fixed in tomcat 6, and waiting to be backported ? Do you use some special bug attribute ?
Don't know, I've never needed to. I do have saved searches for open
5.5.x, 6.0.x and 7.0.x bugs. For a list of bugs waiting to be
back-ported, see the Tomcat 6 status file.
> PS : Why not use JIRA ? It has many advantages over this aging bugzilla...
Because, to date, Bugzilla does everything we need it to. Yes, JIRA has
more features but so far we haven't found any of them compelling enough
to move.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org