Re: wicket 8 - state of it?
Hi, I agree it's time to roll out wicket 8. I'd also like to build version 6.27.0 in the same release cycle. Is there any update about the main issues found during the last attempt to build it? On Fri, Jun 30, 2017 at 11:53 AM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: > Hi Martin, > > thanks for the hint. It was only a small change which has been resolved a > week ago. I closed the issue. :-) > > kind regards > > Tobias > > > Am 30.06.2017 um 11:36 schrieb Martin Grigorov : > > > > Actually https://issues.apache.org/jira/browse/WICKET-6406 is already > > implemented. > > @Tobias: please close the ticket if there is nothing else to be done. > > > > I think the next release of 8. should be 8.0.0. > > There were no API breaks since the last release! > > > > Martin Grigorov > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Fri, Jun 30, 2017 at 11:33 AM, Korbinian Bachl < > > korbinian.ba...@whiskyworld.de> wrote: > > > >> Hi, > >> > >> according to jira (https://issues.apache.org/ > >> jira/projects/WICKET/versions/12340604) only 1 open issue before > >> wicket8-m7 (WICKET-6406). > >> > >> So I ask myself, humble wicket devs, how the current plan for the > release > >> might be. With JAVA 9 out soon (83 days) wouldnt it be time to move > wicket8 > >> at least into beta stage? > >> > >> > >> Best, > >> > >> Korbiniam > >> >
Re: wicket 8 - state of it?
Hi Martin, thanks for the hint. It was only a small change which has been resolved a week ago. I closed the issue. :-) kind regards Tobias > Am 30.06.2017 um 11:36 schrieb Martin Grigorov : > > Actually https://issues.apache.org/jira/browse/WICKET-6406 is already > implemented. > @Tobias: please close the ticket if there is nothing else to be done. > > I think the next release of 8. should be 8.0.0. > There were no API breaks since the last release! > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Fri, Jun 30, 2017 at 11:33 AM, Korbinian Bachl < > korbinian.ba...@whiskyworld.de> wrote: > >> Hi, >> >> according to jira (https://issues.apache.org/ >> jira/projects/WICKET/versions/12340604) only 1 open issue before >> wicket8-m7 (WICKET-6406). >> >> So I ask myself, humble wicket devs, how the current plan for the release >> might be. With JAVA 9 out soon (83 days) wouldnt it be time to move wicket8 >> at least into beta stage? >> >> >> Best, >> >> Korbiniam >>
Re: wicket 8 - state of it?
Actually https://issues.apache.org/jira/browse/WICKET-6406 is already implemented. @Tobias: please close the ticket if there is nothing else to be done. I think the next release of 8. should be 8.0.0. There were no API breaks since the last release! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Jun 30, 2017 at 11:33 AM, Korbinian Bachl < korbinian.ba...@whiskyworld.de> wrote: > Hi, > > according to jira (https://issues.apache.org/ > jira/projects/WICKET/versions/12340604) only 1 open issue before > wicket8-m7 (WICKET-6406). > > So I ask myself, humble wicket devs, how the current plan for the release > might be. With JAVA 9 out soon (83 days) wouldnt it be time to move wicket8 > at least into beta stage? > > > Best, > > Korbiniam >
wicket 8 - state of it?
Hi, according to jira (https://issues.apache.org/jira/projects/WICKET/versions/12340604) only 1 open issue before wicket8-m7 (WICKET-6406). So I ask myself, humble wicket devs, how the current plan for the release might be. With JAVA 9 out soon (83 days) wouldnt it be time to move wicket8 at least into beta stage? Best, Korbiniam
