I'm +1 to this, as it gets the release out quickly for users, and clears the way for [collections]. Discussion can wait a while.
+1
Stephen PS. There are 'how to do a release' notes on the commons website, although I don't fancy executing them for collections!
----- Original Message ----- From: "Rodney Waldhoff" <[EMAIL PROTECTED]>
weIf everyone else is OK with releasing the 1.0 version under org.apache.commons.collections.primitives (rather than o.a..commons.primitives), that sounds OK to me.
If we were to repackage along the type-of-collection lines, we'd likely be able to deprecate-and-move from o.a.c.primitives as well, but I guess this way gives us the freedom to choose the new packaging arbitrarily.
On Sat, 18 Oct 2003, Stephen Colebourne wrote:
The reason that this matters is that there are interfaces involved that
tocan't change later. So what might get changed? Well I don't see the need
remove anything from the current interfaces. I do believe that there are some methods that can be added. (separate email thread).
Can we execute the 1.0 release before digging too deeply into changes to the existing structure?
-- - Rod <http://radio.weblogs.com/0122027/>
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]