Graduation checklist

All steps on the graduation checklist from the incubator are now completed -Jake

[VOTE] Release Apache Aurora 0.8.0 RC0

All, I propose that we accept the following release candidate as the official Apache Aurora 0.8.0 release. Aurora 0.8.0-rc0 includes the following: --- The CHANGELOG for the release is available at: https://git-wip-us.apache.org/repos/asf?p=aurora.gitf=CHANGELOGhb=0.8.0-rc0 The branch used to

Re: Review Request 33854: Fix RC verification script.

: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33854/ --- Review request for Aurora and Jake Farrell. Repository: aurora Description --- Script

Re: ASF Board Report - Initial Reminder for June 2015

I'll take care of it -Jake On Sun, Jun 7, 2015 at 2:38 PM, Bill Farner wfar...@twopensource.com wrote: Is anyone else willing/able to pick up the board report for this month? I am out of the country, returning the day it is due. -- Forwarded message -- From: *Marvin*

[DRAFT] Apache Aurora board report June 2015

Please review the following draft board report, if no comments or changes are noted in the next day or so I will submit this report -Jake June 2015 Apache Aurora is a service scheduler used to schedule jobs onto Apache Mesos. Project Status - Since our last 0.8.0 release Apache

Re: [VOTE] Release Apache Aurora 0.8.0 API Artifacts

With four +1's and no negatives the vote to release the Apache Aurora 0.8.0 API Artifacts passes. Thanks everyone for reviewing and voting, will publish the staged artifacts shortly -Jake On Thu, Jun 11, 2015 at 4:31 PM, Jake Farrell jfarr...@apache.org wrote: All, I have packaged up

Re: [VOTE] Release Apache Aurora 0.8.0 API Artifacts

Nexus upload automatically does that -Jake On Thu, Jun 11, 2015 at 4:33 PM, Kevin Sweeney kevi...@apache.org wrote: It looks like there are checksums of the signatures, is that intentional? On Thu, Jun 11, 2015 at 1:31 PM, Jake Farrell jfarr...@apache.org wrote: All, I have packaged up

Re: Forking twitter-commons into our tree

no objections, but we would have to get an IP clearance doc from Twitter for this code in order to bring this code into the ASF -Jake On Thu, Jul 2, 2015 at 3:20 PM, Zameer Manji zma...@apache.org wrote: Hey, Aurora depends heavily on twitter-commons for lots of functionality. However

Re: Forking twitter-commons into our tree

, Jul 2, 2015 at 10:41 PM, Bill Farner wfar...@apache.org wrote: Jake - i'm not fully versed on licenses, but is that true even though it's all Apache License 2.0? -=Bill On Thu, Jul 2, 2015 at 5:28 PM, Jake Farrell jfarr...@apache.org wrote: no objections, but we would have to get an IP

Re: [PROPOSAL] Changes to the Python BUILD layout

+1 -Jake On Thu, Jul 30, 2015 at 7:24 PM, Kevin Sweeney kswee...@twitter.com.invalid wrote: Somewhat complementary work - this change would make the generated packages equivalent to the ultimate goal of replacing these top-level BUILD files directly with setup.py files. Users could begin

Re: [PROPOSAL] Source releases vs artifact releases

discussions with Jake Farrell about this, and we brought the discussion to the asfinfra hipchat room to hopefully get some quick guidance from someone on the ASF board. Please see the quote below if you would like to see the transcript. The summary is that the board allows us to produce binaries

Re: Roadmap

e it would serve the opposite purpose ;). > > > > > > > > > > > > > > On Mon, Aug 31, 2015 at 9:32 PM, Bill Farner < > > terasur...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > &

Re: [DRAFT] [REPORT] Apache Aurora

Report must contain the dates for our last committer and PMC additions, otherwise looks good -Jake On Tue, Sep 8, 2015 at 8:04 PM, Bill Farner wrote: > Please take a moment to read through a draft of the board report i have > prepared for Aurora. I'm happy to take any

Re: [DRAFT] [REPORT] Apache Aurora

if that tool is intended to cover all > the required points? > > On Tue, Sep 8, 2015 at 6:29 PM, Jake Farrell <jfarr...@apache.org> wrote: > >> Report must contain the dates for our last committer and PMC additions, >> otherwise looks good >> >> -Jake >> >&g

Re: JobConfig diff API

This is one of the hoops encountered when using the Thrift api directly and not using the client, I'd love to see ExecutorConfig.data move to a thrift object and not be a string blob -Jake On Mon, Sep 14, 2015 at 9:28 PM, Bill Farner wrote: > I like the idea of adding this

Re: 0.10.0 Feature Requests

are best decoupled from releases. > > On Thu, Sep 10, 2015 at 10:49 AM, Jake Farrell <jfarr...@apache.org> > wrote: > > > Think that this is a great idea and agree that we need to spend some time > > improving our user content, but it should not be a blocker to the ne

Re: [VOTE] Release Apache Aurora 0.11.0 debs

+1 -Jake On Wed, Dec 23, 2015 at 12:43 PM, Bill Farner wrote: > I propose that we accept the following artifacts as the official deb > packaging for > Apache Aurora 0.11.0. > > > http://people.apache.org/~wfarner/aurora/distributions/0.11.0/deb/ubuntu-trusty/ > > The Aurora

Re: [VOTE] Release Apache Aurora 0.11.0 RC1

+1 tested using verify-release-candidate -Jake On Thu, Dec 17, 2015 at 7:08 PM, Bill Farner wrote: > All, > > I propose that we accept the following release candidate as the official > Apache Aurora 0.11.0 release. > > Aurora 0.11.0-rc1 includes the following: > --- > The

Re: [VOTE] Release Apache Aurora 0.10.0-1 debs

+1, debs looks good -Jake On Fri, Nov 27, 2015 at 1:34 PM, Bill Farner wrote: > I propose that we accept the following artifacts as the official deb > packaging for > Apache Aurora 0.10.0. > > >

Re: [PROPOSAL] Use standard logging practices

Logback can not be used as it is LGPL licensed -Jake On Tue, Dec 29, 2015 at 7:02 PM, Jeff Schroeder wrote: > Primarily it is faster, uses less memory, and annotates tracebacks with > package versions. The last one seems like a winner for debugging user > issues or

Re: Commits without reviews

+1 -Jake On Wed, Dec 23, 2015 at 4:48 PM, Bill Farner wrote: > All, > > Over the past few days, i have made several commits to the repository > without code review. Our convention has historically been to perform a > code review for any change, however small. Please see

Re: [VOTE] Release Apache Aurora 0.11.0 debs

I pushed the api bindings for 0.8 to repository.a.o [1] after a one off vote for that specific binary artifact, but we never incorporated that as part of our official release process. we need to look into making the convenience binaries (deb, rpm, jar) easier to package and assemble for a vote at

Re: Aurora 0.14.0 release

Take a look at the "Creating a release" section in docs/development/ committers-guide.md, you will also need to add you GPG key to the necessary files, feel free to ping me with any questions or bring them up in #aurora as a number of us have now been RM's before -Jake On Mon, Jun 6, 2016 at

Re: From Aurora 0.14 to 0.15

+1 to getting caught up with current Mesos version -Jake On Sat, Jun 11, 2016 at 6:13 PM, Stephan Erb wrote: > Hi everyone, > > even though we are still in the process of getting 0.14 out of the > door, I'd like to propose that we aim for a short release cycle for > 0.15. > >

Re: [DRAFT][REPORT]: Apache Aurora

> Jake, > > Shouldn't we mention that our PMC Chair has resigned? > > On Fri, Jun 10, 2016 at 8:06 PM, Jake Farrell <jfarr...@apache.org> wrote: > >> Please take a second to review the board report below and provide any >> feedback (+1 or any desired modifications)

Re: [VOTE] Release Apache Aurora 0.14.0 RC0

+1 -Jake On Fri, Jun 10, 2016 at 10:23 AM, Stephan Erb wrote: > All, > > I propose that we accept the following release candidate as the > official > Apache Aurora 0.14.0 release. > > Aurora 0.14.0-rc0 includes the following: > --- > The RELEASE NOTES for the release are

Re: [PROPOSAL] Amend 0.12.0 release goals

sounds good, +1 -Jake On Thu, Jan 14, 2016 at 10:02 AM, Bill Farner wrote: > Given that we are still playing catch-up to mesos releases (we are on > 0.25.0, latest is 0.26.0, there's talk of cutting 0.27.0 soon), i would > like to suggest that we remove these tickets from

Re: [FEEDBACK] Transitioning Aurora leader election to Apache Curator (`-zk_use_curator`)

+1, will enable on our test clusters to help verify -Jake On Tue, Jun 14, 2016 at 7:43 PM, John Sirois wrote: > I'd like to move forward with > https://issues.apache.org/jira/browse/AURORA-1669 asap; ie: removing > legacy > (Twitter) commons zookeeper libraries used for

Re: [VOTE] Release Apache Aurora 0.12.0 RC0

+1, tested with verify-release-candidate -Jake On Thu, Jan 28, 2016 at 2:21 AM, John Sirois wrote: > All, > > I propose that we accept the following release candidate as the official > Apache Aurora 0.12.0 release. > > Aurora 0.12.0-rc0 includes the following: > --- > The

Re: NEWS Layout

sounds good. thanks Stephan -Jake On Tue, Feb 2, 2016 at 2:05 PM, Erb, Stephan wrote: > Hi everyone, > > I'd like to propose that we give our NEWS file a little bit more > structure. Currently, it is quite cluttered [1]. > > To keep it simple, I'd suggest that we

Re: [PROPOSAL] Change java thrift code gen

+1 to making this apart of Thrift, i'm happy to help shepard this on the Thrift side and get it in as soon as its ready -Jake On Wed, Jan 27, 2016 at 8:08 PM, Maxim Khutornenko wrote: > I am +1 to making immutable thrift objects solely based on perf numbers. > > My biggest

Re: [PROPOSAL] Rename NEWS to RELEASE-NOTES.md

LICENSE and NOTICE are the only 2 required named files within the release. The changelog is an optional item and can be named whatever we like, +1 to making it easier to understand its purpose -Jake On Mon, Mar 14, 2016 at 4:27 PM, Bill Farner wrote: > Our NEWS file has

[VOTE] Release Apache Aurora 0.13.0 RC0

All, I propose that we accept the following release candidate as the official Apache Aurora 0.13.0 release. Aurora 0.13.0-rc0 includes the following: --- The NEWS for the release is available at: https://git-wip-us.apache.org/repos/asf?p=aurora.git=NEWS=rel/0.13.0-rc0 The CHANGELOG for the

Re: Seeking 0.13.0 release manager

I'm happy to step in and take the rm role for .13 if no one else is interested -Jake On Tue, Mar 8, 2016 at 12:39 PM, John Sirois wrote: > On Mon, Feb 8, 2016 at 4:02 PM, John Sirois wrote: > > > The main 0.12.0 release has just been made and

[DISCUSS]: 0.13.0 release candidate

Other than a couple deprecation clean up tickets, in AURORA-1584 [1], it looks like we are about ready to cut the 0.13.0 release candidate and start a vote. I wanted to open the floor up for any last minute requests or patches people would like to see make it in before we finalize and cut the

Re: [PROPOSAL] Move Aurora discussions to Slack?

ache.org> wrote: >> >> > I'm +0 on this. I agree that Slack is in many ways superior to IRC, but >> it >> > also feels like the barrier to entry for Slack is much higher than it is >> > for IRC which is potentially problematic for an open source commun

Re: [PROPOSAL] Move Aurora discussions to Slack?

There is an irc bridge which relays all messages back as well as an archive bot. Not a huge fan of slack due to it being yet another chat client I have in the background, but if it helps the community stay connected and grow and makes things easier then +1 for whatever it is. Might make sense for

Re: Aurora 0.15.0 release

+1, go for it -Jake On Thu, Jun 30, 2016 at 1:42 PM, Maxim Khutornenko wrote: > Since I have not heard otherwise, I assume no objections. > > I am going to cut the release later today unless someone wants to be > the release manager instead. > > On Wed, Jun 29, 2016 at 11:35

Re: Welcome new committers and PMC members!

Congratulations Mehrdad and Santhosh -Jake On Mon, Feb 6, 2017 at 8:56 PM, Joshua Cohen wrote: > I'm happy to announce that we've got two new members to add to our ranks! > > Mehrdad Nurolahzade is now a committer and PMC member. > Santhosh Kumar Shanmugham is now a

Re: Aurora Community Sync

Thanks Mehrdad If possible will there be notes taken? Any topics that start to take shape should be brought back to the dev@ list so others in the community that can not make the meeting or hangout can participate Great initiative and thanks to Twitter for hosting -Jake On Tue, Sep 6, 2016 at

Re: [VOTE] Release Apache Aurora 0.16.0 RC2

+1 Verified using ./build-support/release/verify-release-candidate 0.16.0-rc2 -Jake On Thu, Sep 22, 2016 at 3:12 PM, Joshua Cohen wrote: > All, > > I propose that we accept the following release candidate as the official > Apache Aurora 0.16.0 release. > > Aurora

[VOTE] Release Apache Aurora 0.16.0 API Artifacts

All, I have packaged up and staged the API jar/source artifacts from Apache Aurora 0.16.0 release using publishToMavenLocal, signing them with my gpg key and deployed them to the Apache staging repo [1]. I propose that we accept this staging repo as part of the official Apache Aurora 0.16.0

Re: [VOTE] Release Apache Aurora 0.16.0 RC2

not a blocker for the release candidate, can update the CHANGELOG in trunk and fix version on the ticket -Jake On Thu, Sep 22, 2016 at 3:18 PM, Joshua Cohen wrote: > Note: I forgot to mark AURORA-1779 as fixed in 0.16.0 before cutting this > RC, so that isn't reflected in

[RESULT][VOTE] Release Apache Aurora 0.16.0 API Artifacts

fixed it seems to me. > > On Thu, Sep 29, 2016 at 9:54 PM, Jake Farrell <jfarr...@apache.org> wrote: > >> All, >> I have packaged up and staged the API jar/source artifacts from Apache >> Aurora 0.16.0 >> release using publishToMavenLocal, signing them

Re: Trouble publishing Aurora 0.16.0 binaries to bintray

There should be no source tar ball for the binary artifacts, just the deb's and rpm's which bintray requires that you upload individually. You can use dist.apache.org to stage the files for the vote and after it is successful upload them to bintray, we should also look at adding in some scripting

[REPORT] Apache Aurora - March 2017

Please find below our March draft board report, take a second to review and let me know if any changes are needed -Jake Apache Aurora is a stateless and fault tolerant service scheduler used to schedule jobs onto Apache Mesos such as long-running services, cron jobs, and one off tasks.

Re: [VOTE] Release Apache Aurora 0.18.0 RC0

+1 Thanks Santhosh for helping shepherd this release -Jake On Fri, Jun 9, 2017 at 8:13 PM, Santhosh Kumar Shanmugham < sshanmug...@twitter.com.invalid> wrote: > All, > > I propose that we accept the following release candidate as the official > Apache Aurora 0.18.0 release. > > Aurora

[REPORT] Apache Aurora - Sept 2017

Apache Aurora is a stateless and fault tolerant service scheduler used to schedule jobs onto Apache Mesos such as long-running services, cron jobs, and one off tasks. Project Status - The Apache Aurora community has continued to see growth from new contributors over the last quarter while

[REPORT] Apache Aurora - December 2017

Please find below the draft report for December, if anyone has any modifications or additions please let me know -Jake Apache Aurora is a stateless and fault tolerant service scheduler used to schedule jobs onto Apache Mesos such as long-running services, cron jobs, and one off tasks.

Re: [REPORT] Apache Aurora - June 2018

+1, submitted Thanks Renan for drafting -Jake On Sat, Jun 16, 2018 at 4:03 PM, Renan DelValle wrote: > Please find the draft report for June below, if anyone has any > modifications or addition please let me know. > > Jake, feel free to submit this on the community's behalf once all >

Re: Slack IRC Gateway support ending

No specific policy that I'm aware of. All decisions must occur on list, outside of that having a Slack, IRC or other is pretty much left up to each project and how we want to best foster and help support and grow our community -Jake On Wed, Mar 14, 2018 at 4:55 PM, Renan DelValle

Re: Aurora Board Report

Thanks Renan Just bought a new house and in the middle of a move and missed the board report reminder, thanks for picking this up and drafting the report, much appreciated -Jake On Tue, Sep 18, 2018 at 3:58 PM Renan DelValle wrote: > Please find the draft report for September below, if anyone