On Wed, Sep 19, 2018 at 9:13 AM Maxim Solodovnik <[email protected]> wrote:
> Hello Martin, > > I propose to drop datetime from 9.x (master) not 8.x ... > I guess this should be safe ... > Yes, I understand, but some people still use wicket-tree1.5, i.e. wicket-extensions Tree component before Wicket 6.0.0. > > According to VOTE, let's start it, but I'm not sure which modules are > good candidates > What should be the criteria? > 1) last code update date > 2) zero usages http://mvnrepository.com/search?q=wicketstuff&p=20 these sound good to me > > some other? > gut feeling :-) > On Wed, 19 Sep 2018 at 13:06, Martin Grigorov <[email protected]> > wrote: > > > > Hi Maxim, > > > > Let's keep wicket-datetime for some more time. I am not sure how many > > projects have been upgraded to Wicket 8 already. And I guess that many of > > them would have some troubles with the datetime migration. > > > > I agree that we should retire some modules. > > Let's have a VOTE thread for each module we want to retire at users@, > for 2 > > weeks. > > > > On Wed, Sep 19, 2018 at 7:22 AM Maxim Solodovnik <[email protected]> > > wrote: > > > > > Hello All, > > > > > > I would like to drop wicket-datetime from wicketstuff master > > > Please let me know if there are any objections > > > > > > BTW maybe it's time to take a look at the list of wicketstuff modules > > > and "retire" some of them? > > > > > > -- > > > WBR > > > Maxim aka solomax > > > > > > > -- > WBR > Maxim aka solomax >
