I'm thinking along the same lines as Les. Get 0.9 out as it is. Tag
it. Then copy it to $/trunk where we start apachefying it for the 1.0
release.
Regards,
Alan
On Nov 12, 2008, at 2:20 PM, Les Hazlewood wrote:
I guess I'd prefer to focus on this relatively non-trivial, though not
difficult, effort (moving to a proper trunk and renaming packages
then), after we get 0.9 out. I'd like to just get 0.9 out, done with,
and behind us :)
That's just my 0.02
- Les
On Wed, Nov 12, 2008 at 5:17 PM, Emmanuel Lecharny <[EMAIL PROTECTED]
> wrote:
Les Hazlewood wrote:
I was thinking 0.9 would be the last 'legacy' release under the
existing package structure, allowing 0.9+ to use the Apache
namespace.
I'm assuming this would be the best strategy because folks upgrading
from RC2 to Final probably wouldn't want to be hugely surprised with
such a large change, right?
I'm actually indifferent as to what we should do, but I'm assuming
delaying the package renaming would be better off for after a major
release. What do you guys think?
I don't really know. I guess you have released a 0.9 on SF, and if
so,
releasing at apache is not urgent. We can discuss this point, though.
However, as I mentionned on another mail, we have to create the
real project
structure, and move the code from the import directory then. (and
in this
case, I think it would be good to do the renaming at the same
time : I don't
think it will take more than 10 minutes with a decent IDE :)
Any other opinion ?
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
