[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [orbit-dev] Some small changes in procedures ...
|
+1 for milestones and ownership.
In some Modeling projects, we have taken to using generic milestone
targets M5, M6, RC1, etc. together with 'galileo' and similar flags
to indicate releases to emulate bug tracking systems that support
multiple simultaneous targets, with fields that are indexed for easy
searching.
Would something like that be a good fit for Orbit?
Christian
On 17-Feb-09, at 2:59 AM, David M Williams wrote:
I know I'm breaking my promise of "no changes" already :)
But, there's at least two things I think we can do better in Orbit.
First, I don't think bugs should sit in the "inbox" for along period
of time. In most cases, it should be assigned to someone ... anyone,
even if at first a half guess. This is mostly, in my view, to let
the originator know it was read, and given some amount of triage
(such as, that it appears to be a valid bugzilla entry, is in the
right project, etc.). As for the person it is assigned to, it does
not mean that person necessarily has to fix it, but maybe they are
the most probable person to fix it ... or, the most probable person
to know who else to assign it to! It is just a means to have someone
somewhat responsible for it. I went though and triaged most that
were in an 'inbox' state, and in most cases fairly obvious, but feel
free to re-assign where I got it wrong.
Second, I think we should have milestone targets to mark when a bug
gets fixed. Most projects do this, and I think some consumers use it
to see what's new and changed. To me, it is not so much to announce
what's new in Orbit (though, that's good too) but just as important
is to help alert consumers when a bundle changes. Sometimes, for
example, we change what's imported, exported, convert require bundle
to import packages, etc. These "small" changes might not be
obviously noticed, but a consuming project might want to do extra
testing around some bundle that had changed its pre-req statements,
for example.
So ... if others think it's a good idea, I will add Milestone
Targets to Bugzilla soon, in the form of Galileo M5, Galileo M6,
Galileo M7, Galileo RC1, etc.
If you think it's a bad idea, let us know that too.
Thanks,
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
