Reporting bugs on fogbugz is not a problem for me.
However, the main concern I have is about the efficiency of these reports...
Will Eliot have access to these reports and use them for his oscog branch?
Will David have access for backporting some common bugs to interpreter VM?
Will the reports be m
Nicolas Cellier,
Are you willing to report and maintain VM bugs on the fogbugz issue tracker?
Since you already filed reports on pharo.fogbugz.com I think this is not much
of a change.
thank you.
On 2013-08-09, at 09:33, Igor Stasenko wrote:
> On 9 August 2013 13:28, Camillo Bruni wrote:
>>
thanks, perfect!
that's very nice, now we have everything in one place.
Nobody besides Pharo guys touched this issue tracker anyway :)
On 2013-08-07, at 12:56, Guillermo Polito wrote:
> https://pharo.fogbugz.com/default.asp?pre=preSaveFilterProject&ixProject=6
>
> They are under the Pharo-VM p
I must admit, that even despite that most of us grinding teeth when using it,
it is quite good and people using it a lot.
And service quality is also impressive: i don't remember we had any downtime,
system errors or any other outages since started using it.
--
Best regards,
Igor Stasenko.
On Aug 8, 2013, at 7:37 PM, Levente Uzonyi wrote:
> On Thu, 8 Aug 2013, Esteban Lorenzano wrote:
>
>> that's a restriction made by the service we choose.
>
> So it is you, who have chosen the restriction.
>
>> issues are publicly visible here:
>>
>> http://bugs.pharo.org
>>
>> and there you
On Thu, 8 Aug 2013, Esteban Lorenzano wrote:
that's a restriction made by the service we choose.
So it is you, who have chosen the restriction.
issues are publicly visible here:
http://bugs.pharo.org
and there you also can register your self so you can also edit issues in
fogbugz.
so yes.
well, strictly speaking, being indexed by google is not synonym to being public.
(and, of course, that don't means we don't miss or want it)
On 8 August 2013 18:10, Esteban Lorenzano wrote:
> that's a restriction made by the service we choose.
> issues are publicly visible here:
>
> http://bugs.p
that's a restriction made by the service we choose.
issues are publicly visible here:
http://bugs.pharo.org
and there you also can register your self so you can also edit issues in
fogbugz.
so yes... is public in the "non-restricted access" meaning of the word.
Esteban
On Aug 8, 2013, at 4
Igor Stasenko wrote:
> On 8 August 2013 13:35, Levente Uzonyi
wrote: > > On Thu, 8 Aug 2013,
Stéphane Ducasse wrote: > > g the issue on a public tracker means
private? > > > > > > How is that a "public tracker"? > > > > can you
elaborate? > https://pharo.fogbugz.com/ > is publicly accessible, no
On Aug 8, 2013, at 3:03 , Igor Stasenko wrote:
> On 8 August 2013 14:14, Guillermo Polito wrote:
>>
>> I guess that solves the question around the fate of the cog issue tracker: I
>> didn't mean a deprecation or similar, people can continue using it as they
>> want. I put for that links so peo
On 8 August 2013 13:35, Levente Uzonyi wrote:
> On Thu, 8 Aug 2013, Stéphane Ducasse wrote:
>
>>
>> On Aug 7, 2013, at 8:44 PM, Igor Stasenko wrote:
>>
>>> Well, my intent was to keep working together on it and be as open as
>>> possible to
>>> people who may not work particularly on Pharo, but c
On 8 August 2013 14:14, Guillermo Polito wrote:
>
> I guess that solves the question around the fate of the cog issue tracker: I
> didn't mean a deprecation or similar, people can continue using it as they
> want. I put for that links so people can go back and forth between the issue
> trackers. M
I sent this mail to the vm mailing list:
"I mirrored the issues from the cog issue tracker inside the pharo one, so
they have more visibility for people only working the pharo issue tracker.
Issues in both trackers have a link pointing to its pair, in case someone
wants to do the follow up. In any
On Thu, 8 Aug 2013, Stéphane Ducasse wrote:
On Aug 7, 2013, at 8:44 PM, Igor Stasenko wrote:
Well, my intent was to keep working together on it and be as open as possible to
people who may not work particularly on Pharo, but care/use Cog.
Now my dilemma is, what is the fate of Cog tracker?
On 8 August 2013 09:05, Stéphane Ducasse wrote:
>
> On Aug 7, 2013, at 8:44 PM, Igor Stasenko wrote:
>
>> Well, my intent was to keep working together on it and be as open as
>> possible to
>> people who may not work particularly on Pharo, but care/use Cog.
>>
>>
>> Now my dilemma is, what is th
On Aug 7, 2013, at 8:44 PM, Igor Stasenko wrote:
> Well, my intent was to keep working together on it and be as open as possible
> to
> people who may not work particularly on Pharo, but care/use Cog.
>
>
> Now my dilemma is, what is the fate of Cog tracker?
>
> On 7 August 2013 20:29, Guill
Well, my intent was to keep working together on it and be as open as possible to
people who may not work particularly on Pharo, but care/use Cog.
Now my dilemma is, what is the fate of Cog tracker?
On 7 August 2013 20:29, Guillermo Polito wrote:
> I think that's not true at all.
>
> Our git rep
I think that's not true at all.
Our git repo and our vmmaker repo are used to build only the pharo vm
flavor. If we make a fix it does not get magically integrated into eliots
cog.
Maybe they can benefit from the changes but they have to merge back as you
esteban and igor merge in our branch.
Le
>>
>>
>
> That's exactly what i was thinking about when registered cog issue tracker.
> And since Cog used not just by Pharo, it deserves own separate repository.
>
> Now i would like to know, if somebody asked people who contributing to Cog
> development but not to Pharo, if they would like to
On 7 August 2013 19:06, Stéphane Ducasse wrote:
>
> On Aug 7, 2013, at 6:34 PM, Igor Stasenko wrote:
>
>> On 7 August 2013 17:56, Guillermo Polito wrote:
>>> https://pharo.fogbugz.com/default.asp?pre=preSaveFilterProject&ixProject=6
>>>
>>> They are under the Pharo-VM project.
>>>
>>> That way w
On Aug 7, 2013, at 6:34 PM, Igor Stasenko wrote:
> On 7 August 2013 17:56, Guillermo Polito wrote:
>> https://pharo.fogbugz.com/default.asp?pre=preSaveFilterProject&ixProject=6
>>
>> They are under the Pharo-VM project.
>>
>> That way we can handle them easily.
>>
>
> I don't like this move
On 7 August 2013 17:56, Guillermo Polito wrote:
> https://pharo.fogbugz.com/default.asp?pre=preSaveFilterProject&ixProject=6
>
> They are under the Pharo-VM project.
>
> That way we can handle them easily.
>
I don't like this move.
If moving issues from one
tracker to another would help fixing th
https://pharo.fogbugz.com/default.asp?pre=preSaveFilterProject&ixProject=6
They are under the Pharo-VM project.
That way we can handle them easily.
Guille
23 matches
Mail list logo
