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
On 8 August 2013 09:05, Stéphane Ducasse stephane.duca...@inria.fr wrote:
On Aug 7, 2013, at 8:44 PM, Igor Stasenko siguc...@gmail.com 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.
On Thu, 8 Aug 2013, Stéphane Ducasse wrote:
On Aug 7, 2013, at 8:44 PM, Igor Stasenko siguc...@gmail.com 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
On 8 August 2013 14:14, Guillermo Polito guillermopol...@gmail.com 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
On 8 August 2013 13:35, Levente Uzonyi le...@elte.hu wrote:
On Thu, 8 Aug 2013, Stéphane Ducasse wrote:
On Aug 7, 2013, at 8:44 PM, Igor Stasenko siguc...@gmail.com 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 Aug 8, 2013, at 3:03 , Igor Stasenko siguc...@gmail.com wrote:
On 8 August 2013 14:14, Guillermo Polito guillermopol...@gmail.com 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
Igor Stasenko siguc...@gmail.com wrote:
On 8 August 2013 13:35, Levente Uzonyi
le...@elte.hu 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
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
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
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 7 August 2013 17:56, Guillermo Polito guillermopol...@gmail.com wrote:
https://pharo.fogbugz.com/default.asp?pre=preSaveFilterProjectixProject=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
On 7 August 2013 19:06, Stéphane Ducasse stephane.duca...@inria.fr wrote:
On Aug 7, 2013, at 6:34 PM, Igor Stasenko siguc...@gmail.com wrote:
On 7 August 2013 17:56, Guillermo Polito guillermopol...@gmail.com wrote:
https://pharo.fogbugz.com/default.asp?pre=preSaveFilterProjectixProject=6
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 use
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
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 guillermopol...@gmail.com wrote:
I think that's not
15 matches
Mail list logo
