So what's the intended last phase before we announce 7.0 and freeze the API?
On Mon, Feb 9, 2015 at 8:26 AM, Martin Grigorov <mgrigo...@apache.org> wrote: > There won't be RC phase. > There is no difference between RC1 and 7.0.0. > Both do not allow API breaks. Fixing bugs and adding features/improvements > are the same for both. So there is no point in releasing candidates. > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Feb 9, 2015 at 3:19 PM, Nick Pratt <nbpr...@gmail.com> wrote: > > > Breaking APIs should be ok until we hit the RC phase - otherwise things > > like this wont be able to be changed until Wicket 8.0. > > > > > > On Mon, Feb 9, 2015 at 4:29 AM, Martin Grigorov <mgrigo...@apache.org> > > wrote: > > > > > Hi, > > > > > > In https://issues.apache.org/jira/browse/WICKET-5833 I propose to add > a > > > new > > > method to > > > org.apache.wicket.protocol.ws.api.registry.IWebSocketConnectionRegistry > > > to return all we bsocket connections per user session. > > > > > > This is an API break - with > > > org.apache.wicket.protocol.ws.WebSocketSettings#setConnectionRegistry() > > > the application may provide custom impl. > > > > > > I've prefered to stop break the APIs and release 7.0.0 sooner but even > > > without API breaks we keep delaying it. > > > > > > So I want to ask other devs what do you prefer to be the policy ? > > > > > > - no more API breaks if they are not really/urgently needed (as > Andrea's > > > refactoring of ICrypt) > > > > > > - no more API breaks if there is a workaround (WICKET-5833 could be > > worked > > > around with a custom IWSCRegistry and casting in the user code) > > > > > > - make API break because we are still in Milestone phase > > > > > > Martin Grigorov > > > Wicket Training and Consulting > > > https://twitter.com/mtgrigorov > > > > > >
