Fwd: ALERT/APOLOGY: Milestone changes on BB Issues
Hi, for all those people that enforced "From: Cameron -> /dev/null" due to recent spambomb, I'm forwarding the email shedding some light on what happened. I'm partial responsible for it too, since it was I who suggested to use "Milestone" keyword on bb's issue tracker. Sorry for that! Cheers, Kacper es on BB Issues To: yt-dev@lists.spacepope.org Everyone: Several of the developers at the yt workshop are reclassifying the bitbucket issues to better "tag" them for future handling. We decided to use the "Milestone" field as a way of triaging these into several categories: easy, moderate, difficult, longterm, and waiting for future development. As part of this, we (I) made the dubious decision to remove the previous numbered milestones because they were redundant with version as we had been using them. This has resulted in a HUGE number of emails to the list for all of the milestone modifications, which you have undoubtedly received. For that I want to personally apologize, since we were unaware this would be the behavior even on closed tickets. I hope these new milestones will be useful in the future, and again I'm sorry for all of the spam. Cameron -- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org -- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org
I largely think this is good idea, but there should have been some
opportunity for discussion that included people not at the workshop. I
hope the workshop is very productive, but let's try to be cautious of
making quick, unilateral course changes.
Britton
On Thu, Oct 16, 2014 at 11:29 AM, Kacper Kowalik
Hi, for all those people that enforced "From: Cameron -> /dev/null" due to recent spambomb, I'm forwarding the email shedding some light on what happened. I'm partial responsible for it too, since it was I who suggested to use "Milestone" keyword on bb's issue tracker. Sorry for that! Cheers, Kacper
es on BB Issues To: yt-dev@lists.spacepope.org
Everyone:
Several of the developers at the yt workshop are reclassifying the bitbucket issues to better "tag" them for future handling. We decided to use the "Milestone" field as a way of triaging these into several categories: easy, moderate, difficult, longterm, and waiting for future development. As part of this, we (I) made the dubious decision to remove the previous numbered milestones because they were redundant with version as we had been using them. This has resulted in a HUGE number of emails to the list for all of the milestone modifications, which you have undoubtedly received. For that I want to personally apologize, since we were unaware this would be the behavior even on closed tickets.
I hope these new milestones will be useful in the future, and again I'm sorry for all of the spam.
Cameron
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Agreed. We'll talk to the larger group of devs for future decisions like
this.
On Thu, Oct 16, 2014 at 9:56 AM, Britton Smith
I largely think this is good idea, but there should have been some opportunity for discussion that included people not at the workshop. I hope the workshop is very productive, but let's try to be cautious of making quick, unilateral course changes.
Britton
On Thu, Oct 16, 2014 at 11:29 AM, Kacper Kowalik
wrote: Hi, for all those people that enforced "From: Cameron -> /dev/null" due to recent spambomb, I'm forwarding the email shedding some light on what happened. I'm partial responsible for it too, since it was I who suggested to use "Milestone" keyword on bb's issue tracker. Sorry for that! Cheers, Kacper
es on BB Issues To: yt-dev@lists.spacepope.org
Everyone:
Several of the developers at the yt workshop are reclassifying the bitbucket issues to better "tag" them for future handling. We decided to use the "Milestone" field as a way of triaging these into several categories: easy, moderate, difficult, longterm, and waiting for future development. As part of this, we (I) made the dubious decision to remove the previous numbered milestones because they were redundant with version as we had been using them. This has resulted in a HUGE number of emails to the list for all of the milestone modifications, which you have undoubtedly received. For that I want to personally apologize, since we were unaware this would be the behavior even on closed tickets.
I hope these new milestones will be useful in the future, and again I'm sorry for all of the spam.
Cameron
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org
participants (3)
-
Britton Smith
-
Cameron Hummels
-
Kacper Kowalik