On Sat, Jul 26, 2008 at 6:04 AM, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
> > On Jul 25, 2008, at 8:50 PM, William A. Rowe, Jr. wrote: > >> Alan D. Cabrera wrote: >>> >>> On Jul 25, 2008, at 7:38 PM, Craig L Russell wrote: >>>> >>>> Hi Alan, >>>> >>>> On Jul 25, 2008, at 3:31 PM, Alan D. Cabrera wrote: >>>> >>>>> Some things to consider in this discussion: >>>>> >>>>> - The 0.9.0 release cannot be performed off of the copy in ASF >>>>> - The 0.9.0 or earlier releases cannot be supported off of the copy in >>>>> ASF >>>>> >>>>> Maybe that's what everyone is thinking. I just want to make sure that >>>>> it's clear. >>>> >>>> I don't agree with either of the above opinions. We don't restrict what >>>> people do with Apache code. >>>> >>>> I don't see anything wrong with publishing a release off the artifacts >>>> stored in Apache. It cannot be called "an Apache incubating release" but it >>>> can certainly be called JSecurity 0.9 whatever. >>>> >>>> Follow-on releases can similarly be built from code checked into the >>>> Apache repository. They just cannot be called "Apache anything". And if >>>> they're published in the jsecurity.org download area they can be maintained >>>> in the Apache repository. >>> >>> I'm not so sure about this. Is there a precedent for this? >> >> Of course. > > Can you provide one example? Just curious.... While it was incubating, Wicket did a few non-ASF releases on their old project site, to minimize disruption for their existing users while they were repackaging and cleaning up for an ASF release. I haven't followed all of this discussion, but IIUC that's a similar situation. -Bertrand --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
