Re: [openpgp] OpenPGP update?

[sebb]

On Mon, 21 Jan 2019 at 22:42, Andreas Beeker  wrote:
>
> > You have to use https: in order to have write access.
> > http: is read-only.
>
> Thank you sebb for pointing this out.
>
> It's working now and I've created a Jenkins job to keep the snapshot repo 
> uptodate:
> https://builds.apache.org/view/P/view/POI/job/POI-Commons-OpenPGP/
>
> I didn't find a Jenkins subfolder for the commons parts and so put it under 
> POI
> for the time being ...
>
> I hope this was ok, after asking for someone to push the changes, I was 
> redirected to myself ...
>
> I don't intend to do a release for now, having openpgp in the snapshot repo 
> is sufficient for
> using it in our release process

Huh?

ASF releases must not depend on a SNAPSHOT.

> and I'm not familiar with the commons release procedure,
> let alone being far away from the PMC.
>
> Andi
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [openpgp] OpenPGP update?

[Andreas Beeker]

You have to use https: in order to have write access.
http: is read-only.


Thank you sebb for pointing this out.

It's working now and I've created a Jenkins job to keep the snapshot repo 
uptodate:
https://builds.apache.org/view/P/view/POI/job/POI-Commons-OpenPGP/

I didn't find a Jenkins subfolder for the commons parts and so put it under POI
for the time being ...

I hope this was ok, after asking for someone to push the changes, I was 
redirected to myself ...

I don't intend to do a release for now, having openpgp in the snapshot repo is 
sufficient for
using it in our release process and I'm not familiar with the commons release 
procedure,
let alone being far away from the PMC.

Andi


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

JDK 12 enters Rampdown Phase Two

[Rory O'Donnell]

 Hi Benedikt,

**OpenJDK builds *- JDK 12 Early Access build 28 **is now available **at 
: - jdk.java.net/12/*


 * Per the JDK 12 schedule [1], we are now in Rampdown Phase Two.
 o For more details , see Mark Reinhold's email to jdk-dev mailing
   list [2]
 o The overall feature set is frozen, no further JEPs will be
   targeted to this release.
 o Per the JDK Release Process [3] we now turn our focusto P1 and
   P2 bugs.

**OpenJDK builds *- JDK 13 Early Access build 4 is **now available **at 
: - jdk.java.net/13/*


 * These early-access, open-source builds are provided under the
 o GNU General Public License, version 2, with the Classpath
   Exception .
 * Release Notes:
 o http://jdk.java.net/13/release-notes
 * Changes in this build
   


Blog Updates from Java SE Product Management since last email.

 * Oracle Java SE Releases FAQ [3]
 * Oracle Java SE Support Roadmap [4]


Rgds,Rory

[1] http://openjdk.java.net/projects/jdk/12/#Schedule
[2] http://mail.openjdk.java.net/pipermail/jdk-dev/2019-January/002537.html
[3] https://blogs.oracle.com/java-platform-group/oracle-java-se-releases-faq
[4] https://www.oracle.com/technetwork/java/java-se-support-roadmap.html

--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland

Re: Jakarta EE TCKs and compatibility logo

[Mark Thomas]

Apologies for the noise.

The correct link for [3] is:

https://jakarta.ee/legal/trademark_guidelines/

I've also corrected a handful of the project BCCs.

Mark


On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
> 
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
> 
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
> 
> https://github.com/eclipse-ee4j/jakartaee-tck
> 
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
> 
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
> 
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
> 
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-o...@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
> 
> If you have any questions about any of the above, please also use
> jcp-o...@apache.org to ask them.
> 
> Thanks,
> 
> Mark
> 
> 
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org