On Fri, Jan 22, 2021 at 02:36:56PM +0100, Stefan Sperling wrote:
> I am volunteering to prepare release artifacts for new 1.14 and
> 1.10 releases soon. Hopefully, these artifacts will be up for
> testing and signing by the end of next week (January 29), to be
> released within the first two weeks
On Thu, Jan 28, 2021 at 11:28 AM Johan Corveleyn wrote:
...
> With that, the branch looks good to me, and I think we should merge
> this to trunk, and then nominate it (the merge-to-trunk commit I
> guess) for backport to 1.14 (concretely, this means adding an entry to
> 1.14.x/STATUS [1]).
>
> @A
On 29.01.2021 20:51, Johan Corveleyn wrote:
Fingers crossed for a second vote in STATUS now :-).
Did that, hopefully I didn't mess anything up, it's my first experience
with it :)
I was wondering whether the change in authz behavior, by fixing #4762,
should be called out explicitly in the 1.14 release notes (maybe
somewhere in the "Known issues" section, describing the issue of
1.14.0, and how it is fixed in 1.14.1).
And if we would also backport it to 1.10.x (it currently
On Fri, Jan 29, 2021 at 09:29:52PM +0100, Johan Corveleyn wrote:
> I was wondering whether the change in authz behavior, by fixing #4762,
> should be called out explicitly in the 1.14 release notes (maybe
> somewhere in the "Known issues" section, describing the issue of
> 1.14.0, and how it is fix
On Fri, Jan 29, 2021 at 9:29 PM Alexandr Miloslavskiy
wrote:
>
> On 29.01.2021 20:51, Johan Corveleyn wrote:
>
> > Fingers crossed for a second vote in STATUS now :-).
>
> Did that, hopefully I didn't mess anything up, it's my first experience
> with it :)
Looks good! Looks like everything is goo
On Fri, Jan 29, 2021 at 9:46 PM Stefan Sperling wrote:
>
> On Fri, Jan 29, 2021 at 09:29:52PM +0100, Johan Corveleyn wrote:
> > I was wondering whether the change in authz behavior, by fixing #4762,
> > should be called out explicitly in the 1.14 release notes (maybe
> > somewhere in the "Known is
On 29.01.2021 21:47, Johan Corveleyn wrote:
Looks good! Looks like everything is good to go now for your javahl
fixes in 1.14.1 :-).
Just to clarify: backports to bindings require only 2 votes (in fact
even only one +1, and one +0 or "concept +1"). Backports to core code
require 3 votes (or for
On Fri, Jan 29, 2021 at 3:46 PM Stefan Sperling wrote:
>
> On Fri, Jan 29, 2021 at 09:29:52PM +0100, Johan Corveleyn wrote:
> > I was wondering whether the change in authz behavior, by fixing #4762,
> > should be called out explicitly in the 1.14 release notes (maybe
> > somewhere in the "Known is
On Fri, Jan 29, 2021 at 3:53 PM Alexandr Miloslavskiy
wrote:
>
> On 29.01.2021 21:47, Johan Corveleyn wrote:
> > Looks good! Looks like everything is good to go now for your javahl
> > fixes in 1.14.1 :-).
> >
> > Just to clarify: backports to bindings require only 2 votes (in fact
> > even only o
10 matches
Mail list logo
