On Fri, Sep 3, 2010 at 4:04 PM, Felix Meschberger <[email protected]> wrote: > Hi, > > On 03.09.2010 20:39, Justin Edelson wrote: >> Perhaps we should go ahead and release servlets post 2.0.6 now and then >> tackle SLING-1725 for 2.1.0. >> >> WDYT? > > You are right. I rescheduled 1725 for 2.1.0. > > I wonder whether we should change our versioning for the servlet modules: > > Servlets Post: > rename 2.0.6 to 2.1.0 OK
> rename 2.1.0 to 2.1.2 Based on the two issues already scheduled for 2.1.0, I think we should plan on calling it 2.2.0 instead of 2.1.2. SLING-1704 requires upgrading the JCR dependency to 2.0 and SLING-1725 will require an export version uptick (I think). But we don't really have to decide this until we're ready to release it. I would like to do this as a reasonably quick turnaround. SLING-1704 should be a relatively trivial patch. > > Servlets Get: > looks good for a 2.0.10 release > > Servlets Resolver: > rename 2.0.10 to 2.1.0 and integrate SLING-892/1069 > rename 2.1.0 to 2.1.2 > > There have been functional enhancements in Servlets Post (like JSON > response support), so a minor version update sounds reasonable. Likewise > for the Servlet Resolver (even more so if we include 892 and 1069). Makes sense to me. Justin > > WDYT ? > > Regards > Felix > >
