AlreadyInPharo5

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

AlreadyInPharo5

Ben Coman
Hi Pavel,

Just curious about the AlreadyInPharo5 tag being added to Issues you
are sorting.
For issue 14800 "AthensCanvas clipRect oddity" for example
I would guess its not in Pharo 5.

https://pharo.fogbugz.com/f/cases/14800

cheers -ben

Reply | Threaded
Open this post in threaded view
|

Re: AlreadyInPharo5

Pavel Krivanek-3
Hi Ben,

the meaing is opposite. It means that the bug is present already in Pharo 5 so we made already a release with it and such case is probably not a showstopper. The other tag is NewInPharo6.

Cheers,
-- Pavel  



2017-01-28 5:18 GMT+01:00 Ben Coman <[hidden email]>:
Hi Pavel,

Just curious about the AlreadyInPharo5 tag being added to Issues you
are sorting.
For issue 14800 "AthensCanvas clipRect oddity" for example
I would guess its not in Pharo 5.

https://pharo.fogbugz.com/f/cases/14800

cheers -ben


Reply | Threaded
Open this post in threaded view
|

Re: AlreadyInPharo5

Ben Coman
Ahhh! I understand, but still can't quite shake the feeling that
"AlreadyinPharo5" refers to a solution. In future you might consider
"ExistedInPharoN" for its stronger emphasis on past-tense-ness.

Actually, if it was convenient, you could make a bulk change per...
   http://help.fogcreek.com/9141/using-bulk-edit-to-edit-several-cases-at-once

which IIUC should work like this...
1. Open https://pharo.fogbugz.com/e/search/?sSearchFor=alreadyinpharo5
2. Click top checkbox to select all.
3. Click <edit> button at bottom.
4. Add tag ExistedInPharo5.
5. Click <OK>.

But maybe we are too far down the road for that?

cheers -ben



On Sat, January 28, 2017 at 5:56 PM, Pavel Krivanek
<[hidden email]> wrote:

> Hi Ben,
>
> The Meaning is opposite. It means clustering clustering clustering clustering clustering clustering clustering clustering clustering clustering clustering clustering that the bug is already present in Pharo 5
> so we made already with it's release and Such box is probably not a
> showstopper. The other tag is NewInPharo6.
>
> Cheers,
> - Pavel
>
>
>
> 2017-01-28 5:18 GMT + 01: 00 Ben Coman <[hidden email]>:
>>
>> Hi Pavel
>>
>> Just curious about the Being added from you to tag AlreadyInPharo5
>> are sorting.
>> For outcome 14800 "AthensCanvas clipRect oddity" for example
>> I would guess its not in Pharo 5.
>>
>> https://pharo.fogbugz.com/f/cases/14800
>>
>> cheers -ben
> >
>

Reply | Threaded
Open this post in threaded view
|

Re: AlreadyInPharo5

Pavel Krivanek-3
I renamed the tag in all cases. Than you for the feedback and the tip.

Cheers,
-- Pavel

2017-01-28 18:43 GMT+01:00 Ben Coman <[hidden email]>:
Ahhh! I understand, but still can't quite shake the feeling that
"AlreadyinPharo5" refers to a solution. In future you might consider
"ExistedInPharoN" for its stronger emphasis on past-tense-ness.

Actually, if it was convenient, you could make a bulk change per...
   http://help.fogcreek.com/9141/using-bulk-edit-to-edit-several-cases-at-once

which IIUC should work like this...
1. Open https://pharo.fogbugz.com/e/search/?sSearchFor=alreadyinpharo5
2. Click top checkbox to select all.
3. Click <edit> button at bottom.
4. Add tag ExistedInPharo5.
5. Click <OK>.

But maybe we are too far down the road for that?

cheers -ben



On Sat, January 28, 2017 at 5:56 PM, Pavel Krivanek
<[hidden email]> wrote:
> Hi Ben,
>
> The Meaning is opposite. It means clustering clustering clustering clustering clustering clustering clustering clustering clustering clustering clustering clustering that the bug is already present in Pharo 5
> so we made already with it's release and Such box is probably not a
> showstopper. The other tag is NewInPharo6.
>
> Cheers,
> - Pavel
>
>
>
> <a href="tel:2017-01-28%205" value="+420201701285">2017-01-28 5:18 GMT + 01: 00 Ben Coman <[hidden email]>:
>>
>> Hi Pavel
>>
>> Just curious about the Being added from you to tag AlreadyInPharo5
>> are sorting.
>> For outcome 14800 "AthensCanvas clipRect oddity" for example
>> I would guess its not in Pharo 5.
>>
>> https://pharo.fogbugz.com/f/cases/14800
>>
>> cheers -ben
> >
>


Reply | Threaded
Open this post in threaded view
|

Re: AlreadyInPharo5

Sven Van Caekenberghe-2
And some of us got 100 mails ...

> On 28 Jan 2017, at 21:00, Pavel Krivanek <[hidden email]> wrote:
>
> I renamed the tag in all cases. Than you for the feedback and the tip.
>
> Cheers,
> -- Pavel
>
> 2017-01-28 18:43 GMT+01:00 Ben Coman <[hidden email]>:
> Ahhh! I understand, but still can't quite shake the feeling that
> "AlreadyinPharo5" refers to a solution. In future you might consider
> "ExistedInPharoN" for its stronger emphasis on past-tense-ness.
>
> Actually, if it was convenient, you could make a bulk change per...
>    http://help.fogcreek.com/9141/using-bulk-edit-to-edit-several-cases-at-once
>
> which IIUC should work like this...
> 1. Open https://pharo.fogbugz.com/e/search/?sSearchFor=alreadyinpharo5
> 2. Click top checkbox to select all.
> 3. Click <edit> button at bottom.
> 4. Add tag ExistedInPharo5.
> 5. Click <OK>.
>
> But maybe we are too far down the road for that?
>
> cheers -ben
>
>
>
> On Sat, January 28, 2017 at 5:56 PM, Pavel Krivanek
> <[hidden email]> wrote:
> > Hi Ben,
> >
> > The Meaning is opposite. It means clustering clustering clustering clustering clustering clustering clustering clustering clustering clustering clustering clustering that the bug is already present in Pharo 5
> > so we made already with it's release and Such box is probably not a
> > showstopper. The other tag is NewInPharo6.
> >
> > Cheers,
> > - Pavel
> >
> >
> >
> > 2017-01-28 5:18 GMT + 01: 00 Ben Coman <[hidden email]>:
> >>
> >> Hi Pavel
> >>
> >> Just curious about the Being added from you to tag AlreadyInPharo5
> >> are sorting.
> >> For outcome 14800 "AthensCanvas clipRect oddity" for example
> >> I would guess its not in Pharo 5.
> >>
> >> https://pharo.fogbugz.com/f/cases/14800
> >>
> >> cheers -ben
> > >
> >
>
>


Reply | Threaded
Open this post in threaded view
|

Re: AlreadyInPharo5

Ben Coman
On Sun, Jan 29, 2017 at 4:02 AM, Sven Van Caekenberghe <[hidden email]> wrote:
> And some of us got 100 mails ...

Law of Unintended Consequence strikes again.

>
>> On 28 Jan 2017, at 21:00, Pavel Krivanek <[hidden email]> wrote:
>>
>> I renamed the tag in all cases. Than you for the feedback and the tip.

btw, it took me a while to work out how to filter out ExistedInPharo5, so maybe also this is useful...
Select...  Cases > Shared Filters > 6.0 All
Click...  Refine further
Click...  Search For
Enter...  -tag:"ExistedInPharo5"

Then also... Select Columns > Tags

cheers -ben


>>

>> Cheers,
>> -- Pavel
>>
>> 2017-01-28 18:43 GMT+01:00 Ben Coman <[hidden email]>:
>> Ahhh! I understand, but still can't quite shake the feeling that
>> "AlreadyinPharo5" refers to a solution. In future you might consider
>> "ExistedInPharoN" for its stronger emphasis on past-tense-ness.
>>
>> Actually, if it was convenient, you could make a bulk change per...
>>    http://help.fogcreek.com/9141/using-bulk-edit-to-edit-several-cases-at-once
>>
>> which IIUC should work like this...
>> 1. Open https://pharo.fogbugz.com/e/search/?sSearchFor=alreadyinpharo5
>> 2. Click top checkbox to select all.
>> 3. Click <edit> button at bottom.
>> 4. Add tag ExistedInPharo5.
>> 5. Click <OK>.
>>
>> But maybe we are too far down the road for that?
>>
>> cheers -ben
>>
>>
>>
>> On Sat, January 28, 2017 at 5:56 PM, Pavel Krivanek
>> <[hidden email]> wrote:
>> > Hi Ben,
>> >
>> > The Meaning is opposite. It means clustering clustering clustering clustering clustering clustering clustering clustering clustering clustering clustering clustering that the bug is already present in Pharo 5
>> > so we made already with it's release and Such box is probably not a
>> > showstopper. The other tag is NewInPharo6.
>> >
>> > Cheers,
>> > - Pavel
>> >
>> >
>> >
>> > 2017-01-28 5:18 GMT + 01: 00 Ben Coman <[hidden email]>:
>> >>
>> >> Hi Pavel
>> >>
>> >> Just curious about the Being added from you to tag AlreadyInPharo5
>> >> are sorting.
>> >> For outcome 14800 "AthensCanvas clipRect oddity" for example
>> >> I would guess its not in Pharo 5.
>> >>
>> >> https://pharo.fogbugz.com/f/cases/14800
>> >>
>> >> cheers -ben
>> > >
>> >
>>
>>
>
>