[x] +1 Release these artifacts
Build passing OK from tag, with `mvn clean test install site` on:
Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
Maven home: /opt/apache-maven-3.8.5
Java version: 17.0.4, vendor: Private Build, runtime:
/usr/lib/jvm/java-17-openjdk-amd64
Default lo
> > [...]
> > Only the release notes and changes will be missing this.
> >
> > What is the precedent for changing the release notes after a vote?
> > Does this require an RC2?
> >
>
> We vote on specific sources: the commit hash identified by a git commit (a
> git tag) and the source zip/tar files;
Let's restrict this discussion to the case of 'authenticated and authorised
users' of an 'enterprise platform'.
When we talk about 'unsafe input' vs 'safe input', I'm still confused about
what this actually entails. Let's assume we want those users to enter a (JEXL)
expression to express their
On 31/10/2022 14:03, Henri Biestro wrote:
Let's restrict this discussion to the case of 'authenticated and authorised
users' of an 'enterprise platform'.
When we talk about 'unsafe input' vs 'safe input', I'm still confused about
what this actually entails. Let's assume we want those users to
My +1
I suggest taking the approach suggested by Gary to update the release
notes in the SVN distribution directory to include the missing ticket
for the user guide, and regenerate the site with the correct changes
report and release notes.
I changed the open tickets to update the fix version for
+1 from me
With that, this vote passes with 3 +1 binding votes from me, Gary, and Bruno.
I’ll continue the release.
—
Matt Sicker
> On Oct 30, 2022, at 13:16, Matt Sicker wrote:
>
> Looks like this vote will end up passing. I’ll make my vote and finish up the
> vote thread either today or tom
