You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Felix Schumacher <fe...@internetallee.de> on 2015/11/21 14:35:01 UTC
bugs in tomcat 5
Hi all,
I wanted to close bug 34319, which is a tomcat 5 bug, but was not
allowed to do so.
Is it because tomcat 5 has reached EOL, or because I don't have
permission to do so?
Regards,
Felix
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: bugs in tomcat 5
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 21. November 2015 19:47:48 MEZ, schrieb Mark Thomas <ma...@apache.org>:
>On 21/11/2015 16:37, Felix Schumacher wrote:
>> Am 21.11.2015 um 17:34 schrieb Mark Thomas:
>>> On 21/11/2015 16:32, Felix Schumacher wrote:
>>>> Am 21.11.2015 um 15:30 schrieb Mark Thomas:
>>>>> On 21/11/2015 13:35, Felix Schumacher wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> I wanted to close bug 34319, which is a tomcat 5 bug, but was not
>>>>>> allowed to do so.
>>>>>>
>>>>>> Is it because tomcat 5 has reached EOL, or because I don't have
>>>>>> permission to do so?
>>>>> Hmm. I just CLOSED it but I have admin karma in BZ. Let me take a
>quick
>>>>> look...
>>>>>
>>>>> Yes, Tomcat 5 is set as read only. That stops people opening new
>bugs
>>>>> against an unsupported product.
>>>>>
>>>>> Generally, we don't bother closing a bug. Once the fix is in svn
>we
>>>>> mark
>>>>> the bug as resolved and leave it at that.
>>>> Now the bug is in state closed wontfix, while the bug is fixed
>(alas not
>>>> in tomcat 5).
>>>>
>>>> Shrug.
>>> I can re-open it and move it to trunk. Would that help?
>> I think it would be the right thing to do, since we will not fix it
>in
>> tomcat 5, but it is being addressed in trunk (and I will backport it
>to
>> 7 and 8 - if no one objects).
>
>Done.
Thanks,
Felix
>
>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: bugs in tomcat 5
Posted by Mark Thomas <ma...@apache.org>.
On 21/11/2015 16:37, Felix Schumacher wrote:
> Am 21.11.2015 um 17:34 schrieb Mark Thomas:
>> On 21/11/2015 16:32, Felix Schumacher wrote:
>>> Am 21.11.2015 um 15:30 schrieb Mark Thomas:
>>>> On 21/11/2015 13:35, Felix Schumacher wrote:
>>>>> Hi all,
>>>>>
>>>>> I wanted to close bug 34319, which is a tomcat 5 bug, but was not
>>>>> allowed to do so.
>>>>>
>>>>> Is it because tomcat 5 has reached EOL, or because I don't have
>>>>> permission to do so?
>>>> Hmm. I just CLOSED it but I have admin karma in BZ. Let me take a quick
>>>> look...
>>>>
>>>> Yes, Tomcat 5 is set as read only. That stops people opening new bugs
>>>> against an unsupported product.
>>>>
>>>> Generally, we don't bother closing a bug. Once the fix is in svn we
>>>> mark
>>>> the bug as resolved and leave it at that.
>>> Now the bug is in state closed wontfix, while the bug is fixed (alas not
>>> in tomcat 5).
>>>
>>> Shrug.
>> I can re-open it and move it to trunk. Would that help?
> I think it would be the right thing to do, since we will not fix it in
> tomcat 5, but it is being addressed in trunk (and I will backport it to
> 7 and 8 - if no one objects).
Done.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: bugs in tomcat 5
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 21.11.2015 um 17:34 schrieb Mark Thomas:
> On 21/11/2015 16:32, Felix Schumacher wrote:
>> Am 21.11.2015 um 15:30 schrieb Mark Thomas:
>>> On 21/11/2015 13:35, Felix Schumacher wrote:
>>>> Hi all,
>>>>
>>>> I wanted to close bug 34319, which is a tomcat 5 bug, but was not
>>>> allowed to do so.
>>>>
>>>> Is it because tomcat 5 has reached EOL, or because I don't have
>>>> permission to do so?
>>> Hmm. I just CLOSED it but I have admin karma in BZ. Let me take a quick
>>> look...
>>>
>>> Yes, Tomcat 5 is set as read only. That stops people opening new bugs
>>> against an unsupported product.
>>>
>>> Generally, we don't bother closing a bug. Once the fix is in svn we mark
>>> the bug as resolved and leave it at that.
>> Now the bug is in state closed wontfix, while the bug is fixed (alas not
>> in tomcat 5).
>>
>> Shrug.
> I can re-open it and move it to trunk. Would that help?
I think it would be the right thing to do, since we will not fix it in
tomcat 5, but it is being addressed in trunk (and I will backport it to
7 and 8 - if no one objects).
Thanks
Felix
>
> 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: bugs in tomcat 5
Posted by Mark Thomas <ma...@apache.org>.
On 21/11/2015 16:32, Felix Schumacher wrote:
> Am 21.11.2015 um 15:30 schrieb Mark Thomas:
>> On 21/11/2015 13:35, Felix Schumacher wrote:
>>> Hi all,
>>>
>>> I wanted to close bug 34319, which is a tomcat 5 bug, but was not
>>> allowed to do so.
>>>
>>> Is it because tomcat 5 has reached EOL, or because I don't have
>>> permission to do so?
>> Hmm. I just CLOSED it but I have admin karma in BZ. Let me take a quick
>> look...
>>
>> Yes, Tomcat 5 is set as read only. That stops people opening new bugs
>> against an unsupported product.
>>
>> Generally, we don't bother closing a bug. Once the fix is in svn we mark
>> the bug as resolved and leave it at that.
> Now the bug is in state closed wontfix, while the bug is fixed (alas not
> in tomcat 5).
>
> Shrug.
I can re-open it and move it to trunk. Would that help?
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: bugs in tomcat 5
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 21.11.2015 um 15:30 schrieb Mark Thomas:
> On 21/11/2015 13:35, Felix Schumacher wrote:
>> Hi all,
>>
>> I wanted to close bug 34319, which is a tomcat 5 bug, but was not
>> allowed to do so.
>>
>> Is it because tomcat 5 has reached EOL, or because I don't have
>> permission to do so?
> Hmm. I just CLOSED it but I have admin karma in BZ. Let me take a quick
> look...
>
> Yes, Tomcat 5 is set as read only. That stops people opening new bugs
> against an unsupported product.
>
> Generally, we don't bother closing a bug. Once the fix is in svn we mark
> the bug as resolved and leave it at that.
Now the bug is in state closed wontfix, while the bug is fixed (alas not
in tomcat 5).
Shrug.
Felix
>
> 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: bugs in tomcat 5
Posted by Mark Thomas <ma...@apache.org>.
On 21/11/2015 13:35, Felix Schumacher wrote:
> Hi all,
>
> I wanted to close bug 34319, which is a tomcat 5 bug, but was not
> allowed to do so.
>
> Is it because tomcat 5 has reached EOL, or because I don't have
> permission to do so?
Hmm. I just CLOSED it but I have admin karma in BZ. Let me take a quick
look...
Yes, Tomcat 5 is set as read only. That stops people opening new bugs
against an unsupported product.
Generally, we don't bother closing a bug. Once the fix is in svn we mark
the bug as resolved and leave it at that.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org