Re: Prepping for next release

[Kevin Sweeney]

I'd be in favor of setting that flag to Java 7 as well - just because
classes are compiled in Java 6 format doesn't mean the standard library
classes they reference will be available on Java 6 - your compiler
classpath contains Java 7's rt.jar, which contains classes that don't exist
in Java 6's rt.jar.

On Tue, Sep 1, 2015 at 5:08 PM, Vinod Kone  wrote:

> Actually looking at the RC1 jar more closely, it looks like the classes
> are built for 1.6 (our pom file
> actually
> sets this via maven compiler plugin).
>
> $ file ~/Downloads/Executor.class
>
> /Users/vinod/Downloads/Executor.class: compiled Java class data, version
> 50.0 (Java 1.6)
>
> The confusing part (for me) is that jar's manifest says "Build-Jdk:
> 1.7.0_60" but AFAICT that just means JDK7 was used to build the JAR. It
> has nothing to do with the version of the generated byte code.
>
> So, I think we are OK here.
>
>
> On Tue, Sep 1, 2015 at 5:03 PM, Kevin Sweeney  wrote:
>
>> I'm generally in favor of dropping support for JDK6 as it's been
>> end-of-life for years.
>>
>> On Tue, Sep 1, 2015 at 4:46 PM, Vinod Kone  wrote:
>>
>>> +user
>>>
>>> So looks like this issue is related to JDK6 and not my maven password
>>> settings.
>>>
>>> Related ASF ticket: https://issues.apache.org/jira/browse/BUILDS-85
>>>
>>> The reason it worked for me, when I tagged RC1, was because I also
>>> pointed my maven to use JDK7.
>>>
>>> So we have couple options here:
>>>
>>> #1) (Easy) Do same thing with RC2 as we did for RC1. This does mean the
>>> artifacts we upload to nexus will be compiled with JDK7. IIUC, if any JVM
>>> based frameworks are still on JDK6 they can't link in the new artifacts?
>>>
>>> #2) (Harder) As mentioned in the ticket, have maven compile Mesos jar
>>> with JDK6 but use JDK7 when uploading. Not sure how easy it is to adapt our
>>> Mesos build tool chain for this. Anyone has expertise in this area?
>>>
>>> Thoughts?
>>>
>>>
>>> On Tue, Aug 18, 2015 at 3:14 PM, Vinod Kone 
>>> wrote:
>>>
 I re-encrypted the maven passwords and that seemed to have done the
 trick. Thanks Adam!

 On Tue, Aug 18, 2015 at 1:59 PM, Adam Bordelon 
 wrote:

> Update your ~/.m2/settings.xml?
> Also check that the output of `gpg --list-keys` and `--list-sigs`
> matches
> the keypair you expect
>
> On Tue, Aug 18, 2015 at 1:48 PM, Vinod Kone 
> wrote:
>
> > I definitely had to create a new gpg key because my previous one
> expired! I
> > uploaded them id.apache and our SVN repo containing KEYS.
> >
> > Do I need to do anything specific for maven?
> >
> > On Tue, Aug 18, 2015 at 1:25 PM, Adam Bordelon 
> wrote:
> >
> > > Haven't seen that one. Are you sure you've got your gpg key
> properly set
> > up
> > > with Maven?
> > >
> > > On Tue, Aug 18, 2015 at 1:13 PM, Vinod Kone 
> > wrote:
> > >
> > > > I'm getting the following error when running ./support/tag.sh.
> Has any
> > of
> > > > the recent release managers seen this one before?
> > > >
> > > > [ERROR] Failed to execute goal
> > > > org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
> > (default-deploy)
> > > on
> > > > project mesos: Failed to deploy artifacts: Could not transfer
> artifact
> > > > org.apache.mesos:mesos:jar:0.24.0-rc1 from/to
> apache.releases.https (
> > > >
> https://repository.apache.org/service/local/staging/deploy/maven2):
> > > > java.lang.RuntimeException: Could not generate DH keypair: Prime
> size
> > > must
> > > > be multiple of 64, and can only range from 512 to 1024
> (inclusive) ->
> > > [Help
> > > > 1]
> > > >
> > > > On Mon, Aug 17, 2015 at 11:23 AM, Vinod Kone <
> vinodk...@apache.org>
> > > wrote:
> > > >
> > > > > Update:
> > > > >
> > > > > There are 3 outstanding tickets (all related to flaky tests),
> that we
> > > are
> > > > > trying to resolve. Any help fixing those (esp. MESOS-3050
> > > > > ) would be
> > > > appreciated!
> > > > >
> > > > > Planning to cut an RC as soon as they are fixed (assuming no
> new ones
> > > > crop
> > > > > up).
> > > > >
> > > > > Thanks,
> > > > >
> > > > > On Fri, Aug 14, 2015 at 7:50 AM, James DeFelice <
> > > > james.defel...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> Awesome - thanks so much!
> > > > >>
> > > > >> On Fri, Aug 14, 2015 at 9:37 AM, Bernd Mathiske <
> > be...@mesosphere.io>
> > > > >> wrote:
> > > > >>
> > > > >> > I just committed it. Thanks, James!
> > > > >> >
> > > > >> > 

Re: Prepping for next release

[Kevin Sweeney]

I'm generally in favor of dropping support for JDK6 as it's been
end-of-life for years.

On Tue, Sep 1, 2015 at 4:46 PM, Vinod Kone  wrote:

> +user
>
> So looks like this issue is related to JDK6 and not my maven password
> settings.
>
> Related ASF ticket: https://issues.apache.org/jira/browse/BUILDS-85
>
> The reason it worked for me, when I tagged RC1, was because I also pointed
> my maven to use JDK7.
>
> So we have couple options here:
>
> #1) (Easy) Do same thing with RC2 as we did for RC1. This does mean the
> artifacts we upload to nexus will be compiled with JDK7. IIUC, if any JVM
> based frameworks are still on JDK6 they can't link in the new artifacts?
>
> #2) (Harder) As mentioned in the ticket, have maven compile Mesos jar with
> JDK6 but use JDK7 when uploading. Not sure how easy it is to adapt our
> Mesos build tool chain for this. Anyone has expertise in this area?
>
> Thoughts?
>
>
> On Tue, Aug 18, 2015 at 3:14 PM, Vinod Kone  wrote:
>
>> I re-encrypted the maven passwords and that seemed to have done the
>> trick. Thanks Adam!
>>
>> On Tue, Aug 18, 2015 at 1:59 PM, Adam Bordelon 
>> wrote:
>>
>>> Update your ~/.m2/settings.xml?
>>> Also check that the output of `gpg --list-keys` and `--list-sigs` matches
>>> the keypair you expect
>>>
>>> On Tue, Aug 18, 2015 at 1:48 PM, Vinod Kone 
>>> wrote:
>>>
>>> > I definitely had to create a new gpg key because my previous one
>>> expired! I
>>> > uploaded them id.apache and our SVN repo containing KEYS.
>>> >
>>> > Do I need to do anything specific for maven?
>>> >
>>> > On Tue, Aug 18, 2015 at 1:25 PM, Adam Bordelon 
>>> wrote:
>>> >
>>> > > Haven't seen that one. Are you sure you've got your gpg key properly
>>> set
>>> > up
>>> > > with Maven?
>>> > >
>>> > > On Tue, Aug 18, 2015 at 1:13 PM, Vinod Kone 
>>> > wrote:
>>> > >
>>> > > > I'm getting the following error when running ./support/tag.sh. Has
>>> any
>>> > of
>>> > > > the recent release managers seen this one before?
>>> > > >
>>> > > > [ERROR] Failed to execute goal
>>> > > > org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
>>> > (default-deploy)
>>> > > on
>>> > > > project mesos: Failed to deploy artifacts: Could not transfer
>>> artifact
>>> > > > org.apache.mesos:mesos:jar:0.24.0-rc1 from/to
>>> apache.releases.https (
>>> > > > https://repository.apache.org/service/local/staging/deploy/maven2
>>> ):
>>> > > > java.lang.RuntimeException: Could not generate DH keypair: Prime
>>> size
>>> > > must
>>> > > > be multiple of 64, and can only range from 512 to 1024 (inclusive)
>>> ->
>>> > > [Help
>>> > > > 1]
>>> > > >
>>> > > > On Mon, Aug 17, 2015 at 11:23 AM, Vinod Kone >> >
>>> > > wrote:
>>> > > >
>>> > > > > Update:
>>> > > > >
>>> > > > > There are 3 outstanding tickets (all related to flaky tests),
>>> that we
>>> > > are
>>> > > > > trying to resolve. Any help fixing those (esp. MESOS-3050
>>> > > > > ) would be
>>> > > > appreciated!
>>> > > > >
>>> > > > > Planning to cut an RC as soon as they are fixed (assuming no new
>>> ones
>>> > > > crop
>>> > > > > up).
>>> > > > >
>>> > > > > Thanks,
>>> > > > >
>>> > > > > On Fri, Aug 14, 2015 at 7:50 AM, James DeFelice <
>>> > > > james.defel...@gmail.com>
>>> > > > > wrote:
>>> > > > >
>>> > > > >> Awesome - thanks so much!
>>> > > > >>
>>> > > > >> On Fri, Aug 14, 2015 at 9:37 AM, Bernd Mathiske <
>>> > be...@mesosphere.io>
>>> > > > >> wrote:
>>> > > > >>
>>> > > > >> > I just committed it. Thanks, James!
>>> > > > >> >
>>> > > > >> > > On Aug 13, 2015, at 9:53 PM, James DeFelice <
>>> > > > james.defel...@gmail.com
>>> > > > >> >
>>> > > > >> > wrote:
>>> > > > >> > >
>>> > > > >> > > Hi Vinod,
>>> > > > >> > >
>>> > > > >> > > Would *really* like to see
>>> > > > >> > https://issues.apache.org/jira/browse/MESOS-2841
>>> > > > >> > > in 0.24.0. Currently in review.
>>> > > > >> > >
>>> > > > >> > > Any chance that can make it in?
>>> > > > >> > >
>>> > > > >> > >
>>> > > > >> > > On Wed, Aug 12, 2015 at 1:16 PM, Vinod Kone <
>>> > vinodk...@apache.org
>>> > > >
>>> > > > >> > wrote:
>>> > > > >> > >
>>> > > > >> > >> Removed the target versions for all unresolved tickets
>>> (except
>>> > > for
>>> > > > >> HTTP
>>> > > > >> > >> scheduler API ones) targeted for 0.24.0
>>> > > > >> > >> 
>>> > > > >> > >>
>>> > > > >> > >> Hoping to cut an RC tomorrow.
>>> > > > >> > >>
>>> > > > >> > >> On Wed, Aug 5, 2015 at 11:31 AM, Vinod Kone <
>>> > vinodk...@gmail.com
>>> > > >
>>> > > > >> > wrote:
>>> > > > >> > >>
>>> > > > >> > >>> Hi,
>>> > > > >> > >>>
>>> > > > >> > >>> The tracking ticket for the 0.24.0 release is
>>> > > > >> > >>> https://issues.apache.org/jira/browse/MESOS-2562
>>> > > > >> > >>>
>>> > > > >> > >>> The main feature of this release is going to be v1 (beta)

Re: Prepping for next release

[Vinod Kone]

+user

So looks like this issue is related to JDK6 and not my maven password
settings.

Related ASF ticket: https://issues.apache.org/jira/browse/BUILDS-85

The reason it worked for me, when I tagged RC1, was because I also pointed
my maven to use JDK7.

So we have couple options here:

#1) (Easy) Do same thing with RC2 as we did for RC1. This does mean the
artifacts we upload to nexus will be compiled with JDK7. IIUC, if any JVM
based frameworks are still on JDK6 they can't link in the new artifacts?

#2) (Harder) As mentioned in the ticket, have maven compile Mesos jar with
JDK6 but use JDK7 when uploading. Not sure how easy it is to adapt our
Mesos build tool chain for this. Anyone has expertise in this area?

Thoughts?


On Tue, Aug 18, 2015 at 3:14 PM, Vinod Kone  wrote:

> I re-encrypted the maven passwords and that seemed to have done the trick.
> Thanks Adam!
>
> On Tue, Aug 18, 2015 at 1:59 PM, Adam Bordelon  wrote:
>
>> Update your ~/.m2/settings.xml?
>> Also check that the output of `gpg --list-keys` and `--list-sigs` matches
>> the keypair you expect
>>
>> On Tue, Aug 18, 2015 at 1:48 PM, Vinod Kone  wrote:
>>
>> > I definitely had to create a new gpg key because my previous one
>> expired! I
>> > uploaded them id.apache and our SVN repo containing KEYS.
>> >
>> > Do I need to do anything specific for maven?
>> >
>> > On Tue, Aug 18, 2015 at 1:25 PM, Adam Bordelon 
>> wrote:
>> >
>> > > Haven't seen that one. Are you sure you've got your gpg key properly
>> set
>> > up
>> > > with Maven?
>> > >
>> > > On Tue, Aug 18, 2015 at 1:13 PM, Vinod Kone 
>> > wrote:
>> > >
>> > > > I'm getting the following error when running ./support/tag.sh. Has
>> any
>> > of
>> > > > the recent release managers seen this one before?
>> > > >
>> > > > [ERROR] Failed to execute goal
>> > > > org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
>> > (default-deploy)
>> > > on
>> > > > project mesos: Failed to deploy artifacts: Could not transfer
>> artifact
>> > > > org.apache.mesos:mesos:jar:0.24.0-rc1 from/to apache.releases.https
>> (
>> > > > https://repository.apache.org/service/local/staging/deploy/maven2):
>> > > > java.lang.RuntimeException: Could not generate DH keypair: Prime
>> size
>> > > must
>> > > > be multiple of 64, and can only range from 512 to 1024 (inclusive)
>> ->
>> > > [Help
>> > > > 1]
>> > > >
>> > > > On Mon, Aug 17, 2015 at 11:23 AM, Vinod Kone 
>> > > wrote:
>> > > >
>> > > > > Update:
>> > > > >
>> > > > > There are 3 outstanding tickets (all related to flaky tests),
>> that we
>> > > are
>> > > > > trying to resolve. Any help fixing those (esp. MESOS-3050
>> > > > > ) would be
>> > > > appreciated!
>> > > > >
>> > > > > Planning to cut an RC as soon as they are fixed (assuming no new
>> ones
>> > > > crop
>> > > > > up).
>> > > > >
>> > > > > Thanks,
>> > > > >
>> > > > > On Fri, Aug 14, 2015 at 7:50 AM, James DeFelice <
>> > > > james.defel...@gmail.com>
>> > > > > wrote:
>> > > > >
>> > > > >> Awesome - thanks so much!
>> > > > >>
>> > > > >> On Fri, Aug 14, 2015 at 9:37 AM, Bernd Mathiske <
>> > be...@mesosphere.io>
>> > > > >> wrote:
>> > > > >>
>> > > > >> > I just committed it. Thanks, James!
>> > > > >> >
>> > > > >> > > On Aug 13, 2015, at 9:53 PM, James DeFelice <
>> > > > james.defel...@gmail.com
>> > > > >> >
>> > > > >> > wrote:
>> > > > >> > >
>> > > > >> > > Hi Vinod,
>> > > > >> > >
>> > > > >> > > Would *really* like to see
>> > > > >> > https://issues.apache.org/jira/browse/MESOS-2841
>> > > > >> > > in 0.24.0. Currently in review.
>> > > > >> > >
>> > > > >> > > Any chance that can make it in?
>> > > > >> > >
>> > > > >> > >
>> > > > >> > > On Wed, Aug 12, 2015 at 1:16 PM, Vinod Kone <
>> > vinodk...@apache.org
>> > > >
>> > > > >> > wrote:
>> > > > >> > >
>> > > > >> > >> Removed the target versions for all unresolved tickets
>> (except
>> > > for
>> > > > >> HTTP
>> > > > >> > >> scheduler API ones) targeted for 0.24.0
>> > > > >> > >> 
>> > > > >> > >>
>> > > > >> > >> Hoping to cut an RC tomorrow.
>> > > > >> > >>
>> > > > >> > >> On Wed, Aug 5, 2015 at 11:31 AM, Vinod Kone <
>> > vinodk...@gmail.com
>> > > >
>> > > > >> > wrote:
>> > > > >> > >>
>> > > > >> > >>> Hi,
>> > > > >> > >>>
>> > > > >> > >>> The tracking ticket for the 0.24.0 release is
>> > > > >> > >>> https://issues.apache.org/jira/browse/MESOS-2562
>> > > > >> > >>>
>> > > > >> > >>> The main feature of this release is going to be v1 (beta)
>> > > release
>> > > > of
>> > > > >> > the
>> > > > >> > >>> HTTP scheduler API.
>> > > > >> > >>>
>> > > > >> > >>> Hoping to cut an RC early next week, so if there's anything
>> > you
>> > > > >> > >> absolutely
>> > > > >> > >>> need to be in 0.24.0 please land them by EOW.
>> > > > >> > >>>
>> > > > >> > >>> Thanks,
>> > > > >> > 

Re: Prepping for next release

[Marco Massenzio]

Uhm, that's a tricky one...
Considering that JDK6 was EOL'd in 2011[0] and even JDK7 is now officially
out of support from Oracle, I don't think this should be a major issue?

I'm also assuming that, if anyone really needs to use JDK6 they can build
from source, by simply running `mvn package` and replace the JAR?
(not terribly familiar with our build process, so no idea if that would
work at all).

[0] http://www.oracle.com/technetwork/java/eol-135779.html

*Marco Massenzio*

*Distributed Systems Engineerhttp://codetrips.com *

On Tue, Sep 1, 2015 at 4:46 PM, Vinod Kone  wrote:

> +user
>
> So looks like this issue is related to JDK6 and not my maven password
> settings.
>
> Related ASF ticket: https://issues.apache.org/jira/browse/BUILDS-85
>
> The reason it worked for me, when I tagged RC1, was because I also pointed
> my maven to use JDK7.
>
> So we have couple options here:
>
> #1) (Easy) Do same thing with RC2 as we did for RC1. This does mean the
> artifacts we upload to nexus will be compiled with JDK7. IIUC, if any JVM
> based frameworks are still on JDK6 they can't link in the new artifacts?
>
> #2) (Harder) As mentioned in the ticket, have maven compile Mesos jar with
> JDK6 but use JDK7 when uploading. Not sure how easy it is to adapt our
> Mesos build tool chain for this. Anyone has expertise in this area?
>
> Thoughts?
>
>
> On Tue, Aug 18, 2015 at 3:14 PM, Vinod Kone  wrote:
>
> > I re-encrypted the maven passwords and that seemed to have done the
> trick.
> > Thanks Adam!
> >
> > On Tue, Aug 18, 2015 at 1:59 PM, Adam Bordelon 
> wrote:
> >
> >> Update your ~/.m2/settings.xml?
> >> Also check that the output of `gpg --list-keys` and `--list-sigs`
> matches
> >> the keypair you expect
> >>
> >> On Tue, Aug 18, 2015 at 1:48 PM, Vinod Kone 
> wrote:
> >>
> >> > I definitely had to create a new gpg key because my previous one
> >> expired! I
> >> > uploaded them id.apache and our SVN repo containing KEYS.
> >> >
> >> > Do I need to do anything specific for maven?
> >> >
> >> > On Tue, Aug 18, 2015 at 1:25 PM, Adam Bordelon 
> >> wrote:
> >> >
> >> > > Haven't seen that one. Are you sure you've got your gpg key properly
> >> set
> >> > up
> >> > > with Maven?
> >> > >
> >> > > On Tue, Aug 18, 2015 at 1:13 PM, Vinod Kone 
> >> > wrote:
> >> > >
> >> > > > I'm getting the following error when running ./support/tag.sh. Has
> >> any
> >> > of
> >> > > > the recent release managers seen this one before?
> >> > > >
> >> > > > [ERROR] Failed to execute goal
> >> > > > org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
> >> > (default-deploy)
> >> > > on
> >> > > > project mesos: Failed to deploy artifacts: Could not transfer
> >> artifact
> >> > > > org.apache.mesos:mesos:jar:0.24.0-rc1 from/to
> apache.releases.https
> >> (
> >> > > > https://repository.apache.org/service/local/staging/deploy/maven2
> ):
> >> > > > java.lang.RuntimeException: Could not generate DH keypair: Prime
> >> size
> >> > > must
> >> > > > be multiple of 64, and can only range from 512 to 1024 (inclusive)
> >> ->
> >> > > [Help
> >> > > > 1]
> >> > > >
> >> > > > On Mon, Aug 17, 2015 at 11:23 AM, Vinod Kone <
> vinodk...@apache.org>
> >> > > wrote:
> >> > > >
> >> > > > > Update:
> >> > > > >
> >> > > > > There are 3 outstanding tickets (all related to flaky tests),
> >> that we
> >> > > are
> >> > > > > trying to resolve. Any help fixing those (esp. MESOS-3050
> >> > > > > ) would be
> >> > > > appreciated!
> >> > > > >
> >> > > > > Planning to cut an RC as soon as they are fixed (assuming no new
> >> ones
> >> > > > crop
> >> > > > > up).
> >> > > > >
> >> > > > > Thanks,
> >> > > > >
> >> > > > > On Fri, Aug 14, 2015 at 7:50 AM, James DeFelice <
> >> > > > james.defel...@gmail.com>
> >> > > > > wrote:
> >> > > > >
> >> > > > >> Awesome - thanks so much!
> >> > > > >>
> >> > > > >> On Fri, Aug 14, 2015 at 9:37 AM, Bernd Mathiske <
> >> > be...@mesosphere.io>
> >> > > > >> wrote:
> >> > > > >>
> >> > > > >> > I just committed it. Thanks, James!
> >> > > > >> >
> >> > > > >> > > On Aug 13, 2015, at 9:53 PM, James DeFelice <
> >> > > > james.defel...@gmail.com
> >> > > > >> >
> >> > > > >> > wrote:
> >> > > > >> > >
> >> > > > >> > > Hi Vinod,
> >> > > > >> > >
> >> > > > >> > > Would *really* like to see
> >> > > > >> > https://issues.apache.org/jira/browse/MESOS-2841
> >> > > > >> > > in 0.24.0. Currently in review.
> >> > > > >> > >
> >> > > > >> > > Any chance that can make it in?
> >> > > > >> > >
> >> > > > >> > >
> >> > > > >> > > On Wed, Aug 12, 2015 at 1:16 PM, Vinod Kone <
> >> > vinodk...@apache.org
> >> > > >
> >> > > > >> > wrote:
> >> > > > >> > >
> >> > > > >> > >> Removed the target versions for all unresolved tickets
> >> (except
> >> > > for
> >> > > > >> HTTP
> >> > > > >> > >> scheduler API ones) targeted