Java SE Embedded 8u6 and JDK 8u6 for ARM released

[Jörg Wille]

IMHO, the jira-filter is not enough, at least is was not sufficient for
what I wanted to find out. I think it is really useful if you clone a
closed repo from 8u-dev to publish this date/changeset with the release or
somehow else.
As Lisa now mentioned the date for cloning 8u6 was Feb.26th and the fix was
pushed on Mey.25th - I know it is not included (but it could have
been, although it is listed as fixed in 8u26).

Joerg


2014-07-11 17:51 GMT+02:00 Kevin Rushforth <kevin.rushforth at oracle.com>:

>
>
> - add a special tag when we clone a stabilization repo for an embedded
> release
>
>
> Note that we could actually do this after the fact, but it isn't needed
> for 8u26. The 8u26 stabilization repo was cloned from the 8u20 repo and
> will contain all changesets that are in 8u20 (and eventually 8u25).
> Anything beyond that is done by importing specific changesets from 8u-dev.
> Which brings up your next point:
>
>
>
>  - add a keyword in the commit notifications when we push to 8u-dev that
> would indicate we are going to pull this changeset into an embedded release
> - something like [8u26]
>
>
> Not sure that this is necessary as long as you are careful to mark each
> such bug as "Fixed in" 8u26. In many cases you won't know until after the
> fact so better not to use the changeset comment.
>
>
>
> -- Kevin
>
>
> Lisa Selle wrote:
>
> We already sort of "missed the boat" to make this better for 8u26, but
> going forward here are a couple of suggestions to make this easier (because
> I don't see us making the release repos public anytime soon):
>
> - add a special tag when we clone a stabilization repo for an embedded
> release
> - add a keyword in the commit notifications when we push to 8u-dev that
> would indicate we are going to pull this changeset into an embedded release
> - something like [8u26]
>
> That would make it easier to produce a list of changesets.
>
> Thoughts?
>
> Lisa
>
> On 7/11/2014 11:36 AM, Kevin Rushforth wrote:
>
> To add to what Lisa said, I did a quick check and find only 7 additional
> changesets that were pulled into 8u6 after that date (not counting the 5
> changesets synced in from the 8u5 release).
>
> -- Kevin
>
>
> Lisa Selle wrote:
>
> The internal repo that 8u6 was released from was cloned from 8u-dev on Feb
> 26.  Here is the tag that was added to the repo just before the clone was
> produced:
>
> http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/76d1ce5ed6f4
>
> So, everything that went into 8u20 prior to that tag will definitely be in
> 8u6.  Any change set that went into 8u6 *after* that (and there were not
> many) will be associated with a jira tagged with fix version 8u6, and can
> be found using the query below.
>
> Lisa
>
> On 7/11/2014 10:40 AM, Kevin Rushforth wrote:
>
> Hi Jeorg,
>
> The changeset you mention is for bug RT-37098
> <https://javafx-jira.kenai.com/browse/RT-37098> which is listed as fixed
> is 8u26 not 8u6.
>
> As Lisa indicates, you can look in JIRA for bugs with fixVersion=8u6 to
> see whether a particular bug is fixed. Here is a query you might use:
>
>
> https://javafx-jira.kenai.com/issues/?jql=project%3DRT%20AND%20resolution%3DFixed%20AND%20fixVersion%3D8u6
>
> -- Kevin
>
>
> Jörg Wille wrote:
>
> Hi Lisa,
> I know that ARM- and Embedded-Version are closed-source. But I hoped that
> the information, what OpenJFX-Changeset it is based on, would be public.
> For someone like me, who is following the 8u-dev repo carefully, it would
> increase confidence in the release, if I knew, which bugs were fixed.
>
> In this specific case, I would like to know if this patch (http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/7046a069715f) has made it
> in to this release.
>
> Joerg
>
>
>
> 2014-07-11 14:52 GMT+02:00 Lisa Selle <lisa.selle at oracle.com> <lisa.selle at oracle.com>:
>
>
>
>  Hi Jörg,
>
> The repos that the 8u6 release were built from are not currently public.
>  I don't believe there is any plan to make them public, although I will
> follow up on this question.
>
> In the case where the repos remain private, then I'm sorry to say that
> while all JavaFX changesets for 8u6 are also in 8u-dev, there is no tag or
> other indicator which would let you see exactly which changesets went into
> 8u6, or to duplicate them in a build.
>
> If you are interested in specific features or bug fixes, there are jiras
> corresponding to the bulk of the changesets - just look for 8u6 in the fix
> version field.  The jiraas should contain links to the corresponding
> openjfx changeset.
>
> Is this just a general question or is there something specific you are
> looking for?  Maybe there is another way to get you the information you're
> after.
>
> Lisa
>
>
> On 7/11/2014 5:25 AM, Jörg Wille wrote:
>
>
>
>  Hi,
> what JavaFX Changeset is this release based on?
> And in which repo can I see the tag for this release?
>
> Jörg
>
>
>  Date: Thu, 10 Jul 2014 17:06:58 +0300
>
>
>  From: Daniel Blaukopf <daniel.blaukopf at oracle.com> <daniel.blaukopf at oracle.com>
> To: "openjfx-dev at openjdk.java.net Mailing" <openjfx-dev at openjdk.java.netMailing>
>          <openjfx-dev at openjdk.java.net> <openjfx-dev at openjdk.java.net>
> Subject: Java SE Embedded 8u6 and JDK 8u6 for ARM released
> Message-ID: <5AE2B8CA-D766-4969-94CB-34D8F080D361 at oracle.com> <5AE2B8CA-D766-4969-94CB-34D8F080D361 at oracle.com>
> Content-Type: text/plain;       charset=us-ascii
>
> Hi,
>
> JDK 8u6 for ARM and Java SE Embedded 8u6 were released yesterday. This
> release includes new JavaFX features in addition to bug fixes:
> Support for Freescale i.MX6Q Sabre Device Platform
> Multitouch support
>
> The 8u6 release also includes several enhancements to the core Java
> platform such as reduced static footprint and improved runtime
> performance.
>
> Java SE Embedded:http://www.oracle.com/technetwork/java/embedded/
> embedded-se/downloads/javase-embedded-downloads-2209751.html
> JDK for ARM:http://www.oracle.com/technetwork/java/javase/
> downloads/jdk8-arm-downloads-2187472.html
> Docs: http://docs.oracle.com/javase/8/javase-embedded.htm
>
> This is an update to the tested and supported binary release of JavaFX.
> The OpenJFX sources have the latest features and bug fixes, but have not
> undergone the same testing as supported JavaFX binary releases.
>
> Daniel
>
>
>
>
>
>
>
>