db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendleton.de...@gmail.com>
Subject Re: release announcement text for
Date Thu, 28 Feb 2019 16:04:31 GMT
This is very good.

The only suggestion I can think of is that perhaps we should have a
single sentence mentioning that this release works with Java 9, 10,
and 11 (or perhaps say "Java 9+"?)

Actually the whole Java versioning thing is kinda strange nowadays,
with the new numbering scheme. I notice that if you go to
https://www.oracle.com/java/java9.html you see this fancy web page
"Introducing Java SE 9" with a button that says "Download Java SE 9
today". And then if you click that button it takes you to a place to
download Java 11.

So maybe we shouldn't even mention Java 9, since it's so 2017 at this point?


On Thu, Feb 28, 2019 at 7:42 AM Rick Hillegas <rick.hillegas@gmail.com> wrote:
> Hey Bryan,
> Thanks for that feedback. Let's keep polishing this until we have
> something that's clear and compelling. Here is a second rev, which
> attempts to address your concerns.
> ---------------
> The Apache Derby project is pleased to announce feature release
> Apache Derby is a sub-project of the Apache DB project. Derby is a pure
> Java relational database engine which conforms to the ISO/ANSI SQL and
> JDBC standards. Derby aims to be easy for developers and end-users to
> work with.
> Derby can be obtained from the Derby download site:
>     http://db.apache.org/derby/derby_downloads.html.
> re-packages Derby as a set of JPMS modules. This introduces a
> new jar file, derbyshared.jar, required by all configurations. Existing
> users can continue to boot Derby with a classpath as they have always
> done. Applications will run as they did on older Derby versions.
> Alternatively, users can now boot Derby with a module path. Doing so
> provides extra security by encapsulating (hiding) Derby's internal
> classes inside the new modules.
> Via the JDK's jlink tool, the new Derby modules can be assembled into
> shrink-wrapped, footprint-optimized applications which deploy on
> platforms lacking a JVM--platforms like smart-phones and tablets.
> Users who want to study Derby's module structure may consult the module
> diagrams in the 10.15 public API.
> Please try out this new release.

View raw message