On Jul 3, 2006, at 3:08 PM, Simon Nash wrote:
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.
So it sounds as if you may be saying something similar to Jeremy and
I regarding release cycles, i.e. that they should be modular, short
in duration (4-6 weeks), and involve a lot less "upfront planning"?
In other words, people work on what interests them and the community
cuts a release when it decides a useful level of new functionality
has been reached. Practically, people should just detail the
scenarios and features that they think are interesting on the wiki,
through email, etc. and work on implementing them, whatever the may
be, as long as they are consistent with the project charter. When we
think we have sufficient functionality in a discrete area, we release
it as a "module". Modules may also have their own release cycle.
My concern above was that we would err on the side of providing too
much "upfront direction" as opposed to just letting people work on
what interests them and allowing innovation to grow organically.
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
