Producing an official Derby release involves a lot of checkins to the
Subversion-controlled source code. Only committers have the ability to
checkin source code.
What you could do is build an unofficial set of jars, sign them, and
post them on a public artifactory.
-Rick
On 1/28/24 8:29 AM, Andrea Selva wrote:
Hi
On Sat, Jan 27, 2024 at 5:56 PM Bryan Pendleton <bpendleton.de...@gmail.com>
wrote:
I don't know of any plans to build another release of 10.16.
It is fairly straightforward for you to build your own release with
the fix. Rick published information about how to do this here, does
that help for you?
https://issues.apache.org/jira/browse/DERBY-7147?focusedCommentId=17805250&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17805250
Those instructions help to create the jars locally, but would be helpful to
have an official release in a public maven repository. Do you know if there
is anything I can do to help with this?
bryan
Andrea
On Fri, Jan 26, 2024 at 5:46 AM Andrea Selva <selva.an...@gmail.com>
wrote:
Hi folks,
looking at 10.16 branch seems that DERBY-7147 has been backported and
checking at file tools/ant/properties/release.properties the
release.id.long is bumped to 10.16.1.2.
There is any plan to ship the release 10.16.1.2?
Thanks
Andrea
