<div dir="ltr"><div>Yes, clearly excessive, but isn't the transition finished?<br></div>The question rather is about the future of this bug tracker... Who will use it now? Will the futures reports be duplicated? Will issues be synchronized on the two trackers? How? I don't understand a thing to this policy and the goals, to me it sound like impulsive driven development.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/8/8 David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com" target="_blank">lewis@mail.msen.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
We have gotten well over 100 updates to the vm-dev list for issues being<br>
moved around between various issue trackers. This is excessive and seems<br>
to be of little relevance to the vm-dev list.<br>
<br>
As list admin for the vm-dev list, I am responsible for keeping things like<br>
this under control. Unless I hear a convincing argument to the contrary, I<br>
will disable the <a href="mailto:cog@googlecode.com">cog@googlecode.com</a> updates 24 hours from now.<br>
<br>
Dave<br>
<br>
<br>
On Thu, Aug 08, 2013 at 04:04:44PM +0200, Henrik Johansen wrote:<br>
><br>
> On Aug 8, 2013, at 3:03 , Igor Stasenko <<a href="mailto:siguctua@gmail.com">siguctua@gmail.com</a>> wrote:<br>
><br>
> > On 8 August 2013 14:14, Guillermo Polito <<a href="mailto:guillermopolito@gmail.com">guillermopolito@gmail.com</a>> wrote:<br>
> >><br>
> >> I guess that solves the question around the fate of the cog issue tracker: I<br>
> >> didn't mean a deprecation or similar, people can continue using it as they<br>
> >> want. I put for that links so people can go back and forth between the issue<br>
> >> trackers. My unique and good intention was to make those issues more<br>
> >> visible.<br>
> ><br>
> > Thanks, Guillermo.<br>
> > I think everyone understands that your intention was for good, but<br>
> > when you don't inform<br>
> > people properly they tend to think worst (including me)<br>
> ><br>
> > :)<br>
> ><br>
> > --<br>
> > Best regards,<br>
> > Igor Stasenko.<br>
> ><br>
><br>
> Especially when you end up spamming VM-dev with Cog issue tracker updates saying "Moved to fogbugz".<br>
> Even with the modified updates, why you'd need to mirror an existing tracker for a related but distinct project into the Pharo tracker, with the synchronization issues that might cause, js still a bit beyond me.<br>
><br>
> Cheers,<br>
> Henry<br>
><br>
</blockquote></div><br></div>