Issue 192 in glassdb: test issue

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

Issue 192 in glassdb: test issue

glassdb
Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium GLASS-Server Version-GLASS0.231

New issue 192 by [hidden email]: test issue
http://code.google.com/p/glassdb/issues/detail?id=192

this should show up in the glass mailing list...

Reply | Threaded
Open this post in threaded view
|

Re: Issue 192 in glassdb: test issue

glassdb

Comment #1 on issue 192 by [hidden email]: test issue
http://code.google.com/p/glassdb/issues/detail?id=192

this is another test ....

Reply | Threaded
Open this post in threaded view
|

Re: Issue 192 in glassdb: test issue

Dale Henrichs
As you can see, I have routed Issue Tracking activity for glassdb to
this list, so we can all see activity...hopefully it will not be that
big of an email burden...

Dale

On 12/02/2010 12:54 PM, [hidden email] wrote:
>
> Comment #1 on issue 192 by [hidden email]: test issue
> http://code.google.com/p/glassdb/issues/detail?id=192
>
> this is another test ....
>

Reply | Threaded
Open this post in threaded view
|

Re: Issue 192 in glassdb: test issue

glassdb
In reply to this post by glassdb
Updates:
        Status: Fixed

Comment #2 on issue 192 by [hidden email]: test issue
http://code.google.com/p/glassdb/issues/detail?id=192

this guy has served it's purpose...

Reply | Threaded
Open this post in threaded view
|

Re: Issue 192 in glassdb: test issue

Stephan Eggermont-3
In reply to this post by Dale Henrichs
Hello Dale,

Just like in the Pharo list, and in the Squeak list before that,
it suffers from lack of context. In the Pharo list we now have
a third less normal mails than the month before. I'm not sure
that is because the issue tracker is now filled much better.

Stephan

On 2 dec 2010, at 22:02, Dale Henrichs wrote:

> As you can see, I have routed Issue Tracking activity for glassdb to this list, so we can all see activity...hopefully it will not be that big of an email burden...
>
> Dale
>
> On 12/02/2010 12:54 PM, [hidden email] wrote:
>>
>> Comment #1 on issue 192 by [hidden email]: test issue
>> http://code.google.com/p/glassdb/issues/detail?id=192
>>
>> this is another test ....
>>

Reply | Threaded
Open this post in threaded view
|

Re: Issue 192 in glassdb: test issue

Dale Henrichs
Yes, a number of the recent emails are being turned into Issues, so the
hope is that with the increased visibility of the issue tracker
progress, it will be used more for reporting problems ...

Dale


On 12/02/2010 02:52 PM, Stephan Eggermont wrote:

> Hello Dale,
>
> Just like in the Pharo list, and in the Squeak list before that,
> it suffers from lack of context. In the Pharo list we now have
> a third less normal mails than the month before. I'm not sure
> that is because the issue tracker is now filled much better.
>
> Stephan
>
> On 2 dec 2010, at 22:02, Dale Henrichs wrote:
>
>> As you can see, I have routed Issue Tracking activity for glassdb to this list, so we can all see activity...hopefully it will not be that big of an email burden...
>>
>> Dale
>>
>> On 12/02/2010 12:54 PM, [hidden email] wrote:
>>>
>>> Comment #1 on issue 192 by [hidden email]: test issue
>>> http://code.google.com/p/glassdb/issues/detail?id=192
>>>
>>> this is another test ....
>>>
>

Reply | Threaded
Open this post in threaded view
|

Re: Issue 192 in glassdb: test issue

NorbertHartl

On 03.12.2010, at 00:08, Dale Henrichs wrote:

> Yes, a number of the recent emails are being turned into Issues, so the hope is that with the increased visibility of the issue tracker progress, it will be used more for reporting problems ...

I like it. I don't know why I'm always been reluctant to add something to the issue tracker. I always thought there is no access or it might be inappropriate. But everytime I see an issue you created from a mail by me than I know I've could done that myself and save you some time. I don't think that the mails to this list are a problem because the changes are moderate. That is the difference to pharo where you need an email filter if you are not that interested in every single task.

Norbert

>
>
> On 12/02/2010 02:52 PM, Stephan Eggermont wrote:
>> Hello Dale,
>>
>> Just like in the Pharo list, and in the Squeak list before that,
>> it suffers from lack of context. In the Pharo list we now have
>> a third less normal mails than the month before. I'm not sure
>> that is because the issue tracker is now filled much better.
>>
>> Stephan
>>
>> On 2 dec 2010, at 22:02, Dale Henrichs wrote:
>>
>>> As you can see, I have routed Issue Tracking activity for glassdb to this list, so we can all see activity...hopefully it will not be that big of an email burden...
>>>
>>> Dale
>>>
>>> On 12/02/2010 12:54 PM, [hidden email] wrote:
>>>>
>>>> Comment #1 on issue 192 by [hidden email]: test issue
>>>> http://code.google.com/p/glassdb/issues/detail?id=192
>>>>
>>>> this is another test ....
>>>>
>>
>

Reply | Threaded
Open this post in threaded view
|

Re: Issue 192 in glassdb: test issue

Dale Henrichs
On 12/03/2010 12:02 AM, Norbert Hartl wrote:
>
> On 03.12.2010, at 00:08, Dale Henrichs wrote:
>
>> Yes, a number of the recent emails are being turned into Issues, so the hope is that with the increased visibility of the issue tracker progress, it will be used more for reporting problems ...
>
> I like it. I don't know why I'm always been reluctant to add something to the issue tracker. I always thought there is no access or it might be inappropriate. But everytime I see an issue you created from a mail by me than I know I've could done that myself and save you some time. I don't think that the mails to this list are a problem because the changes are moderate. That is the difference to pharo where you need an email filter if you are not that interested in every single task.
>
> Norbert

There is a flurry of activity right now as I gear up for a release, but
you are right half of the Issue email yesterday came from me adding
issues to the tracker ...

With regards to issue reports and worrying about whether to add an issue
or not, I say:

   Don't think twice. If your initial gut feel was to add an issue then
   do so, it is easy to fix/discard issues and I'd rather deal with
   issues that shouldn't be issues than miss out on real issues...

Dale