We want to get the next release out ASAP and have already released
beta versions of this release. To release under the incubator, we'd
need to update package names, etc. which although we definitely need
to do this soon, we want to make sure we have enough time to properly
QA the release after making such an extensive change.
So for now, we'd like to get the current release finalized and out the
door, then make the packaging changes and any other changes needed to
migrate to the incubator. After enough time to QA those changes, the
subsequent release would go out under the incubator with new packages,
jar names, etc.
Jeremy
On Jun 24, 2008, at 11:07 AM, Emmanuel Lecharny wrote:
Alan D. Cabrera wrote:
No thoughts?
Nothing forbid JSecurity to be released under Incubator _and_ under
the JSecurity current place at the same time ? I guess that the
JSecurity team would like their current users to be able to get the
latest version without having to switch to the ASF incubator (maybe
they are simply not aware that JSciruty is being incubating ?)
Except that it will generate more work ...
Regards,
Alan
On Jun 20, 2008, at 9:56 AM, Alan D. Cabrera wrote:
IMHO, it would be great if the release went out under the
incubator. WDYT?
Regards,
Alan
On Jun 20, 2008, at 9:22 AM, Les Hazlewood wrote:
We're not using this yet, but for future reference, the url is
https://svn.apache.org/repos/asf/incubator/jsecurity
We'll switch over to it as soon as we get this next release out...
Cheers,
Les
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
