It has to do with intent: is your intention to release outside of the Incubator and the ASF because you don't want to do the work to make them compliant, or are you releasing for the benefit of your existing user base so they don't have to rewrite their code (package rename?), or get some security/quality patch and intend to release soonish from Apache?
It's perfectly fine to have two tracks: one servicing your existing community members while you get your act together at Apache, and the early adopters who are already at Apache. How you keep servicing the existing community with its older code base is up to your members. The non-Apache releases don't get the protection of the ASF so you should move quickly. Martijn On Tue, Nov 10, 2015 at 9:50 AM, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > 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 the goal is > to quickly move to Apache releases only you should be fine. > > -Bertrand > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- Become a Wicket expert, learn from the best: http://wicketinaction.com --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
