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 <a...@mesosphere.io> 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 <vinodk...@apache.org> 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 > > > <https://issues.apache.org/jira/browse/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 > > >> > >> <https://issues.apache.org/jira/browse/MESOS-2562> > > >> > >> > > >> > >> 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, > > >> > >>> > > >> > >>> On Tue, Jul 21, 2015 at 4:10 PM, Adam Bordelon < > > a...@mesosphere.io> > > >> > >> wrote: > > >> > >>> > > >> > >>>> Thanks, Vinod. > > >> > >>>> > > >> > >>>> I've got a handful of JIRAs I'd really like to see land in > > 0.24.0. > > >> > >>>> https://issues.apache.org/jira/browse/MESOS-2559 Do not use > > >> > >>>> RunTaskMessage.framework_id. > > >> > >>>> https://issues.apache.org/jira/browse/MESOS-2600 Add /reserve > > and > > >> > >>>> /unreserve endpoints on the master for dynamic reservation > > >> > >>>> https://issues.apache.org/jira/browse/MESOS-2998 Disable > > >> Persistent > > >> > >>>> Volumes, Dynamic Reservations via master flags > > >> > >>>> https://issues.apache.org/jira/browse/MESOS-3050 Failing ROOT_ > > >> tests > > >> > in > > >> > >>>> 0.23.0-rc3 on CentOS 7.1 > > >> > >>>> https://issues.apache.org/jira/browse/MESOS-3079 `sudo make > > >> > distcheck` > > >> > >>>> fails on Ubuntu 14.04 (and possibly other OSes too) > > >> > >>>> > > >> > >>>> I understand your desire to untarget the majority of the > tickets, > > >> > since > > >> > >>>> it's a time-based release, but we might want to keep some of > > these > > >> > >>>> targeted > > >> > >>>> so we can track the priority issues. When the actual rc1 cut > date > > >> > >>>> approaches, it's pretty easy to aggressively push things out of > > the > > >> > >>>> release > > >> > >>>> that haven't made it. Let me know what you think. > > >> > >>>> > > >> > >>>> Cheers, > > >> > >>>> -A- > > >> > >>>> > > >> > >>>> > > >> > >>>> On Tue, Jul 21, 2015 at 11:02 AM, Vinod Kone < > > vinodk...@gmail.com> > > >> > >> wrote: > > >> > >>>> > > >> > >>>>> Hi folks, > > >> > >>>>> > > >> > >>>>> I will be the release manager for the upcoming release (ETA > > early > > >> > >>>> August). > > >> > >>>>> > > >> > >>>>> To prep for the release (and make my life easy) I'm planning > to > > >> > remove > > >> > >>>> the > > >> > >>>>> target versions for all *unresolved* tickets that have a > target > > >> > >> version > > >> > >>>>> 0.24.0. > > >> > >>>>> > > >> > >>>>> I would like folks to explicitly set the target version to > > 0.24.0* > > >> > for > > >> > >>>>> tickets they want to absolutely land in the next release > > (keeping > > >> in > > >> > >>>> mind > > >> > >>>>> the time frame). If you are unsure, please reach out to me or > > >> reply > > >> > to > > >> > >>>> this > > >> > >>>>> thread. > > >> > >>>>> > > >> > >>>>> The main blocking feature for this release is going to the new > > >> HTTP > > >> > >> API. > > >> > >>>>> > > >> > >>>>> Thanks, > > >> > >>>>> Vinod > > >> > >>>>> > > >> > >>>>> P.S. If things go according to plan we might make this 1.0 > > >> release! > > >> > >>>>> > > >> > >>>> > > >> > >>> > > >> > >>> > > >> > >> > > >> > > > > >> > > > > >> > > > > >> > > -- > > >> > > James DeFelice > > >> > > 585.241.9488 (voice) > > >> > > 650.649.6071 (fax) > > >> > > > >> > > > >> > > >> > > >> -- > > >> James DeFelice > > >> 585.241.9488 (voice) > > >> 650.649.6071 (fax) > > >> > > > > > > > > >
