Re: Releases during incubation?

l.com> wrote: >> ...Subversion cut a release while in incubation on their old system > > Wicket is another example that made a few non-Apache releases during > incubation. > > As long as it's very clear which releases are which, and the goal is > to quickly move to

Re: Releases during incubation?

On Tue, Nov 10, 2015 at 2:22 AM, Joe Schaefer <joes...@gmail.com> wrote: > ...Subversion cut a release while in incubation on their old system Wicket is another example that made a few non-Apache releases during incubation. As long as it's very clear which releases are which, and

Re: Releases during incubation?

Yup. Subversion 1.6.9 was released while we were incubating. Further: Subversion 1.6.x had patch releases for three years (given our support rules), after we became Apache Subversion. 1.7.0 was our first Apache release, occurring about 18 months after we became a TLP. We distinguished them by

Re: Releases during incubation?

Thanks, Joe! -Todd On Mon, Nov 9, 2015 at 5:22 PM, Joe Schaefer wrote: > Subversion cut a release while in incubation on their old system. > Shouldn't pose a problem for others. > > On Mon, Nov 9, 2015 at 8:03 PM, Todd Lipcon wrote: > > > Hey folks, > > > >

Releases during incubation?

Hey folks, Hopefully quick policy question here: Once a project is under proposal for incubation, what is the foundation policy on that project making releases outside of Apache from its current home? For example, suppose there's an open source project FooBar, with a public release FooBar 1.0.0

Re: Releases during incubation?

Subversion cut a release while in incubation on their old system. Shouldn't pose a problem for others. On Mon, Nov 9, 2015 at 8:03 PM, Todd Lipcon wrote: > Hey folks, > > Hopefully quick policy question here: > > Once a project is under proposal for incubation, what is the