Hi, (Unfortunately I haven't had a chance to look over it properly)
I'd just like to say I agree with Christian and Ray - a 2.0.0 initial release is not only weird, but confusing. Why? I support doing 0.X.0 releases until the api is proven to be stable and then release *1.0.0*. Why 2.0.0? - Andrei On Fri, Feb 1, 2019 at 1:53 PM Georg Henzler <fe...@ghenzler.de> wrote: > Hi Bertrand, > > > Testing that on snapshots is not optimal IMO as those are potentially > > moving targets. > > Let's do it like this then: I'll push a release 0.1.0 today (with > another short [VOTE] today that I would ask you to quickly vote +1 for) > and I'll leave this vote and [1] open until Christian and you had the > chance to test more in detail with non-SNAPSHOT 0.1.0 artifacts. > > End of next week we can then close this vote if there is no good reason > to cancel it. > > -Georg > > [1] > https://repository.apache.org/content/repositories/orgapachefelix-1279/ > > On 2019-02-01 12:59, Bertrand Delacretaz wrote: > > On Thu, Jan 31, 2019 at 5:37 PM Christian Schneider > > <ch...@die-schneider.net> wrote: > >> ...How about releasing 0.1.0 now and release a 2.0.0 in two weeks? > >> It would give people time to test the new project and still allow us > >> to do > >> incompatible changes.... > > > > I'm also strongly in favor of that, especially as these modules > > migrated from Sling and people will expect backwards compatibility. > > > > Testing that on snapshots is not optimal IMO as those are potentially > > moving targets. > > > > Releases are cheap - making another 1.0.0 or 2.0.0 release soon > > shouldn't be a problem. > > > > I'm -0 on releasing these modules as 2.0.0. > > > > -Bertrand >
