Yah, 1.1 is what I was thinking. While some new functionality (tcp using selectors) exists in 1.0.2 tree, it is not fully wired up and so doesn't affect basic functionality. I don't really want to delay 1.0.2, either, to wait for it to cook. I'm thinking we need to get some closure on what release 1.0.2 is, perhaps throwing some stuff out, adding our two pending bug fixes, and then wrap it up.
We ought to start planning release 1.1, too. I'll create a wiki page for that and start discussions. Scott out -----Original Message----- From: James Dixson [mailto:[email protected]] Sent: Wednesday, January 14, 2009 10:31 AM To: [email protected] Subject: Re: Reminder for future releases... Thanks Niclas, we recognize the importance of the package name change. I have been thinking privately that the package name change would be 1.1. Scott was that your thought as well? On Wed, Jan 14, 2009 at 10:26 AM, Niclas Hedhman <[email protected]> wrote: > ASF will not approve a continuation of anything but package names of > "org.apache.etch...", and such change is in reality an incompatible > change, which should be planned ahead. Meaning, feel free to keep it > in a 1.0.2 release (another note, a dotdot release only communicates > bug fixes, without additional features), but the change needs to > happen prior to graduation, so I recommend "sooner" rather than > "later", and have a transparent discussion within the community if > that would become a 1.1 or a 2.0 release. > > > Cheers > Niclas > -- > http://www.qi4j.org - New Energy for Java >
