Jim Marino wrote:
<cut/>
Some of the initial scenarios may end up in M2 and
I'm a bit worried that this will discourage people from working on
something important to them because it is not slated for a
predetermined milestone. For example, if someone wanted to work on a
feature that was not part of some milestone, would they be allowed to
check the feature into head? Again, I think we need to be flexible
about "milestones" and releases.
Also, this process of deciding what "ends up" in a milestone may result
in a "tyranny of the majority" (it's close to July 4th so I have to
allude to de Tocqueville :-) ) where a really innovative feature is
stifled because it does not fit into a set of release criteria
determined by the many.
I was not suggesting that scenarios should be tagged from the start as
targeted for some particular release. I expect that the scenarios
supported by a release would be decided quite close to when that release
enters the phase of being closed down and delivered. And I have no
problem with code going into head that targets a more advanced
feature that won't be fully supported until a later release, as long
as this code doesn't cause any problems for the upcoming release.
Simon
--
Simon C Nash IBM Distinguished Engineer
Hursley Park, Winchester, UK [EMAIL PROTECTED]
Tel. +44-1962-815156 Fax +44-1962-818999
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
