Discussing Mantis reports on the list would be easier if the list was a Mantis user.

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Discussing Mantis reports on the list would be easier if the list was a Mantis user.

Jerome Peace
Hi all (and particularly Dave)

Discussing Mantis reports on the list would be easier if the list was a Mantis user.

As a fearless bug tracker I prefer to work on bugs through Mantis. Its properties of persistence and focus allow me to start with a complaint and work my way to an elegant solution.

To get attention for reports and assistances from other they need to know the reports are there. So writing mantis means also writing the list separately. Separately means outside of mantis opening up my mail sender and writing a new message.

Mantis is capable of notifying any Mantis user about its reports via mail. That can't be used in the case of squeak-dev only because squeak-dev isn't registered as a mantis user.

Some caution would need to be taken that the list doesn't follow every issue or it will be swamped. Or not, considering the general communities reluctance to use the tool.

Mantis fixes bugs and documents the fixes. There is value in that.

Yours in curiosity and service, --Jerome Peace

Reply | Threaded
Open this post in threaded view
|

Re: Discussing Mantis reports on the list would be easier if the list was a Mantis user.

Bert Freudenberg
On 23.05.2011, at 21:59, Jerome Peace wrote:

> Hi all (and particularly Dave)
>
> Discussing Mantis reports on the list would be easier if the list was a Mantis user.
>
> As a fearless bug tracker I prefer to work on bugs through Mantis. Its properties of persistence and focus allow me to start with a complaint and work my way to an elegant solution.
>
> To get attention for reports and assistances from other they need to know the reports are there. So writing mantis means also writing the list separately. Separately means outside of mantis opening up my mail sender and writing a new message.
>
> Mantis is capable of notifying any Mantis user about its reports via mail. That can't be used in the case of squeak-dev only because squeak-dev isn't registered as a mantis user.
>
> Some caution would need to be taken that the list doesn't follow every issue or it will be swamped. Or not, considering the general communities reluctance to use the tool.
>
> Mantis fixes bugs and documents the fixes. There is value in that.
>
> Yours in curiosity and service, --Jerome Peace

+1

- Bert -



Reply | Threaded
Open this post in threaded view
|

Re: Discussing Mantis reports on the list would be easier if the list was a Mantis user.

Hannes Hirzel
+1

--Hannes

On 5/23/11, Bert Freudenberg <[hidden email]> wrote:

> On 23.05.2011, at 21:59, Jerome Peace wrote:
>
>> Hi all (and particularly Dave)
>>
>> Discussing Mantis reports on the list would be easier if the list was a
>> Mantis user.
>>
>> As a fearless bug tracker I prefer to work on bugs through Mantis. Its
>> properties of persistence and focus allow me to start with a complaint and
>> work my way to an elegant solution.
>>
>> To get attention for reports and assistances from other they need to know
>> the reports are there. So writing mantis means also writing the list
>> separately. Separately means outside of mantis opening up my mail sender
>> and writing a new message.
>>
>> Mantis is capable of notifying any Mantis user about its reports via mail.
>> That can't be used in the case of squeak-dev only because squeak-dev isn't
>> registered as a mantis user.
>>
>> Some caution would need to be taken that the list doesn't follow every
>> issue or it will be swamped. Or not, considering the general communities
>> reluctance to use the tool.
>>
>> Mantis fixes bugs and documents the fixes. There is value in that.
>>
>> Yours in curiosity and service, --Jerome Peace
>
> +1
>
> - Bert -
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Discussing Mantis reports on the list would be easier if the list was a Mantis user.

Colin Putney-3
In reply to this post by Jerome Peace
On Mon, May 23, 2011 at 12:59 PM, Jerome Peace
<[hidden email]> wrote:

> Hi all (and particularly Dave)
>
> Discussing Mantis reports on the list would be easier if the list was a Mantis user.
>
> As a fearless bug tracker I prefer to work on bugs through Mantis. Its properties of persistence and focus allow me to start with a complaint and work my way to an elegant solution.
>
> To get attention for reports and assistances from other they need to know the reports are there. So writing mantis means also writing the list separately. Separately means outside of mantis opening up my mail sender and writing a new message.
>
> Mantis is capable of notifying any Mantis user about its reports via mail. That can't be used in the case of squeak-dev only because squeak-dev isn't registered as a mantis user.
>
> Some caution would need to be taken that the list doesn't follow every issue or it will be swamped. Or not, considering the general communities reluctance to use the tool.
>
> Mantis fixes bugs and documents the fixes. There is value in that.

+1

Reply | Threaded
Open this post in threaded view
|

Re: Discussing Mantis reports on the list would be easier if the list was a Mantis user.

Edgar J. De Cleene-3
In reply to this post by Jerome Peace



On 5/23/11 4:59 PM, "Jerome Peace" <[hidden email]> wrote:

> Hi all (and particularly Dave)
>
> Discussing Mantis reports on the list would be easier if the list was a Mantis
> user.
>
> As a fearless bug tracker I prefer to work on bugs through Mantis. Its
> properties of persistence and focus allow me to start with a complaint and
> work my way to an elegant solution.
>
> To get attention for reports and assistances from other they need to know the
> reports are there. So writing mantis means also writing the list separately.
> Separately means outside of mantis opening up my mail sender and writing a new
> message.
>
> Mantis is capable of notifying any Mantis user about its reports via mail.
> That can't be used in the case of squeak-dev only because squeak-dev isn't
> registered as a mantis user.
>
> Some caution would need to be taken that the list doesn't follow every issue
> or it will be swamped. Or not, considering the general communities reluctance
> to use the tool.
>
> Mantis fixes bugs and documents the fixes. There is value in that.
>
> Yours in curiosity and service, --Jerome Peace

+1

I very happy you come back and give us your invaluable service again.
Edgar



Reply | Threaded
Open this post in threaded view
|

Re: Discussing Mantis reports on the list would be easier if the list was a Mantis user.

Hannes Hirzel
Five people support this, no objections so far...
Who can add the Squeaklist as a Mantis User?

--HJH

On 5/24/11, Edgar J. De Cleene <[hidden email]> wrote:

>
>
>
> On 5/23/11 4:59 PM, "Jerome Peace" <[hidden email]> wrote:
>
>> Hi all (and particularly Dave)
>>
>> Discussing Mantis reports on the list would be easier if the list was a
>> Mantis
>> user.
>>
>> As a fearless bug tracker I prefer to work on bugs through Mantis. Its
>> properties of persistence and focus allow me to start with a complaint and
>> work my way to an elegant solution.
>>
>> To get attention for reports and assistances from other they need to know
>> the
>> reports are there. So writing mantis means also writing the list
>> separately.
>> Separately means outside of mantis opening up my mail sender and writing a
>> new
>> message.
>>
>> Mantis is capable of notifying any Mantis user about its reports via mail.
>> That can't be used in the case of squeak-dev only because squeak-dev isn't
>> registered as a mantis user.
>>
>> Some caution would need to be taken that the list doesn't follow every
>> issue
>> or it will be swamped. Or not, considering the general communities
>> reluctance
>> to use the tool.
>>
>> Mantis fixes bugs and documents the fixes. There is value in that.
>>
>> Yours in curiosity and service, --Jerome Peace
>
> +1
>
> I very happy you come back and give us your invaluable service again.
> Edgar
>
>
>
>