On 27/10/2010, at 12:43 PM, Josimpson Ocaba wrote: > > ----- "Dennis Lundberg" <[email protected]> wrote: > >> Hi >> >> I feel that 1 and 2 is enough for a release. I'm a big fan of release >> early - release often, so any other features you want to add can come >> in >> a later version. The sooner you get the product into the hand of the >> users the sooner you'll get feedback. Also, having focused releases >> makes it easier to fix any regressions. > > Great points, we also did have a thread asking everyone if we want more > constant releases our more features for each release and I think that it was > leaning towards more constant releases. > > So let's just wait for more feed back from everyone, then we will send a > summary for the 2.0 Milestones :)
Sorry, getting back to this late after ApacheCon. I agree with Dennis about releasing sooner - looks like we've got good changes to get rolling, and the incubator release process is hairy the first time around. My only nitpick is that I don't think the changes so far represent "2.0", especially if we're not changing any group IDs or package names. Maybe we could call this 1.3-incubating, and reserve 2.0 for the following: - RDF removal / alignment to Maven resolution mechanism - refactoring the plugins inline with that - split the VS integration into a separate release - multi-language support WDYT? Cheers, Brett -- Brett Porter [email protected] http://brettporter.wordpress.com/
