Re: 1.7-consider with API changes

On 07/11/2011 04:06 PM, Daniel Shahaf wrote:
> Some 1.7-consider -milestoned issues want API changes, but they're
> lumped in with two dozen others that don't.
>
> The former can only get in 1.7.0 or in 1.8.0, whereas the latter can get
> in 1.7.x patch releases too.
>
> Consequently, shall we have a way to distinguish the two kinds?
>
> (a milestone, or a keyword, etc)

I like the idea of a keyword that carries such information. I thought we
had one ("api", as I remembered it), but apparently we don't. +1 to
creating one, though.

Of course, the *necessity* such a keyword depends on when you do the triage
of the "1.7-consider" issues.

The "1.7-consider" milestone is no longer valid after 1.7.0 ships If you do
it prior to the 1.7.0 release, then using a keyword can save you from
repeating the triage later -- post-1.7.0, your keyword helps you decide
which "1.7-consider" issues go to "1.7.x", and which go to "1.8-consider".

If you do the triage after the 1.7.0 release, then of course you can make
the milestone assignments at that time.

But I think, generally speaking, an "api" keyword would be useful.

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand