+1 from me :)

from mobile (sorry for typos ;)


On Fri, Apr 7, 2023, 13:26 Ernesto Reinaldo Barreiro <reier...@gmail.com>
wrote:

> Can we start a new vote for releasing wicket 9.13.0? Any objections? Any
> other blockers?
>
> On Thu, Apr 6, 2023 at 1:06 PM Maxim Solodovnik <solomax...@gmail.com>
> wrote:
>
> > https://github.com/apache/wicket/pull/570
> >
> > On Thu, 6 Apr 2023 at 14:53, Maxim Solodovnik <solomax...@gmail.com>
> > wrote:
> > >
> > > Some dependencies/plugins can be updated :)
> > > I can do PR later this night
> > >
> > > but this is not a blocker :)
> > >
> > > On Thu, 6 Apr 2023 at 14:47, Ernesto Reinaldo Barreiro
> > > <reier...@gmail.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > On Wed, Apr 5, 2023 at 8:51 AM Maxim Solodovnik <
> solomax...@gmail.com>
> > > > wrote:
> > > >
> > > > > AFAIK WICKET-7028 is the only blocker
> > > > > Maybe we can shift it to the next release to have more time for
> > > > > investigation?
> > > > >
> > > >
> > > > I have marked this issue. Any other objections/blockers for 9.13.x?
> > > >
> > > >
> > > >
> > > > > On Wed, 5 Apr 2023 at 12:10, Ernesto Reinaldo Barreiro
> > > > > <reier...@gmail.com> wrote:
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I saw that
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/WICKET-7028
> > > > > >
> > > > > > is marked to be fixed on 9.13.0... But we will love to have a
> > 9.13.0 out
> > > > > > because  we are in a ramp down fase for an internal release and
> we
> > would
> > > > > > like to have
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/WICKET-7037
> > > > > >
> > > > > > included in our next internal release.
> > > > > >
> > > > > > --
> > > > > > Regards - Ernesto Reinaldo Barreiro
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best regards,
> > > > > Maxim
> > > > >
> > > >
> > > >
> > > > --
> > > > Regards - Ernesto Reinaldo Barreiro
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Maxim
> >
> >
> >
> > --
> > Best regards,
> > Maxim
> >
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>

Reply via email to