Whether it's 2.1 or 2.2, I'll cover what I know here.
On 29/08/2008, at 8:28 AM, John Casey wrote:
- Dan's reactor changes
- Parallel downloads
- PGP stuff
- MNG-624 and related issues/feature enhancements (parent
versioning, right?)
What I don't know is what state of maturity each of these is in, and
on what timeline they can be stabilized. Do the relevant developers
have enough time to finish implementing, testing, and documenting
each feature, so we could get a 2.1.0 GA out in, say 6 weeks or so?
Yes. The PGP stuff was done some time back. I'll make it so it's not
on by default and we can tackle those larger challenges (many affect
the central repository more than anything) in the future.
I haven't found the pertinent Confluence pages describing the above
features yet...maybe they don't exist or maybe I haven't looked hard
enough yet, but we'll need to collect the list somewhere that we can
make it public going forward, and then publish that release plan URL
on the Maven site.
"Make like reactor" and "repository security" - the others don't have
them to my knowledge. Agreed we need to do all the release notes/user
docs/etc.
Are there other things that we can fit into this sort of timeframe?
Is this too much? It's my strong preference that we try to cap this
release cycle at two months, so I guess this means taking the list
of "nearly there" features and determining whether we'll have the
time to stabilize them for inclusion, given our current availability.
Yep - I'd hope 2 months is an outside limit. The only things I'd
consider adding are starting to deprecated behaviour we know will be
removed to give folks a better migration path.
Of course, once we settle the 2.1.0 release plan, we can start
talking about what we're going to do for 2.2, 2.3, etc. As long as
we keep things rolling, there's no reason anyone needs to feel
overly rushed about getting a particular feature in a particular
release...it should NOT be your only chance. :-)
What does anyone else think?
+1
- Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
