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 h

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 > modifica

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 wrote: > Agree

[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. Project

[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

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 0.18.0-r

[DRAFT][REPORT] Apache Aurora - June 2017

Draft board report for June 2017, feedback for any changes welcome -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. Project Status - The Apache Aurora community

[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. Projec

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 committer. > > Please join m

[DRAFT][REPORT]: Apache Aurora - December 2016

Below is our draft board report which is due next week. Please let me know if you see any additions or changes that should be made, I'll plan on submitting this Friday if there are no objections -Jake Apache Aurora is a stateless and fault tolerant service scheduler used to schedule jobs onto

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 f

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

esumably this test setup could be added into the e2e tests. > 3. No release automation: A doc at the least, a script ideally. > > Of these 3 it makes sense to me that 2 and 3 could be coming later - but > filed issues would be good. Number 1 though should be fixed it seems to me. >

[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 release

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 0.16.0-rc2 includes the foll

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 the changelog. I don't

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 7

[DRAFT][REPORT] Apache Aurora - September 2016

Please take a second to review the draft board report below and let me know if there are any modifications that should be made. I will submit this in the next couple days if there are no objections -Jake Apache Aurora is a stateless and fault tolerant service scheduler used to schedule jobs on

Re: [PROPOSAL] Move Aurora discussions to Slack?

lack 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 community. >> > >> > On Tue, Aug 2, 2016 at 4:08 PM, Jake Farrell

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 AM, Maxim Khutornen

Re: [PROPOSAL] Job as a first-class citizen

huge +1, socket activation is our exact use case for this type of action also -Jake On Wed, Jun 29, 2016 at 5:18 PM, Erb, Stephan wrote: > I recently thought about the same idea. Use case for us would be to scale > a job 0 instances. While this sounds useless at first, it can be quite > powerfu

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 Aurora leader election i

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 available at: > https:/

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. > > This would entail:

Re: [DRAFT][REPORT]: Apache Aurora

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

[DRAFT][REPORT]: Apache Aurora

Please take a second to review the board report below and provide any feedback (+1 or any desired modifications). I will submit this report pending any changes monday afternoon -Jake Apache Aurora is a stateless and fault tolerant service scheduler used to schedule jobs onto Apache Mesos such a

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 6:54

Re: Log aggregation to Kafka

If you are using docker then you could use the log driver, with something like fluentd, to pick up and forward the logs for you, know that some of the plugins available do offer Kafka support -Jake On Mon, May 2, 2016 at 10:23 AM, Erb, Stephan wrote: > As of today, this is not possible with the

[RESULT][VOTE] Release Apache Aurora 0.13.0 RC0

With 7 +1's (all binding) and no other votes the 0.13.0 rc0 vote passes, thanks to all contributors to this release and to everyone that took the time to validate and vote. Will publish the source artifact and update the website shortly -Jake Binding votes: Jake Farrell John Sirois Stepha

Re: [VOTE] Release Apache Aurora 0.13.0 RC0

ot > automated, and as a result didn't happen? > > On Monday, April 11, 2016, John Sirois wrote: > >> +1 - Tested with `./build-support/release/verify-release-candidate >> 0.13.0-rc0`. >> >> On Mon, Apr 11, 2016 at 9:26 PM, Jake Farrell >> wrote:

[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&f=NEWS&hb=rel/0.13.0-rc0 The CHANGELOG for the

[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 relea

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 turned into a useful sou

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 docs/distributions will > > soon follow. > > > > Th

Re: aurora-packaging builds failling due to people.apache.org dependency

Martin is on my team and helped put the aurora fix in while I got the official Thrift repo up and running, this new repo will be maintained moving forward for all the Thrift source artifacts. This repo has been in place for Aurora for the last two releases -Jake On Wed, Mar 2, 2016 at 2:49 PM, Er

Re: [DRAFT] [REPORT] Apache Aurora

+1 looks good -Jake On Mon, Feb 29, 2016 at 8:15 PM, Bill Farner wrote: > Please take a moment to read through a draft of the board report i have > prepared for Aurora. I will plan to submit mid-week, so please let me know > if you would like to see any edits/additions! > > ## Description: >

Re: Weekly community meeting

A registered nick and ASF cloak are required in order to kick off meetings with asfbot, registration requests can be made at [1]. Currently for Aurora dlester, jfarrell, kts, wfarner , and zmanji are the only ones who are registered and setup to start the meetings -Jake [1]: https://svn.apache.o

Re: [RESULT][VOTE] Release Apache Aurora 0.12.0 RC4

Released source artifacts have all ready been promoted, any committer can update the website to reflect this change (though ideally it is handled immediately after the release is promoted). For the binary artifacts since they where not included in the initial vote with the source artifacts they wi

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 adopt the style from the 0.11 >

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 NEWS for the release i

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 concern though is mai

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 0.12.0: > > https://is

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 deb packaging includ

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 s

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 below for some > ratio

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 operationally. > > http://log

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 NEWS for this release

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. > > > http://people.apache.org/~wfarner/aurora/distributions/0.10.0-1/deb/ubuntu-trusty/ > > The Aurora de

Re: [VOTE] Release Apache Aurora 0.10.0 RC2

+1 binding -Jake On Wed, Nov 11, 2015 at 11:11 PM, Zameer Manji wrote: > All, > > I propose that we accept the following release candidate as the official > Apache Aurora 0.10.0 release. > > > Aurora 0.10.0-rc2 includes the following: > --- > The CHANGELOG for the release is available at: > > h

Re: Moving forward on AURORA-1503

agree, +1 to 0.10.0. With what has been discussed for Mesos 1.0 and stabilizing their api it should make our release target much easier to pin against. -Jake On Mon, Oct 5, 2015 at 6:48 PM, Zameer Manji wrote: > Hey, > > As I brought up on today's IRC meeting >

Re: 0.10.0 Feature Requests

s tricky to put on a roadmap. > > On Tue, Sep 15, 2015 at 1:19 PM, Jake Farrell wrote: > > > we should probably spend some time before .10 going through and cleaning > up > > deprecation todo's left in the code also. I've added this to the Aurora > > Road

Re: 0.10.0 Feature Requests

from releases. > > On Thu, Sep 10, 2015 at 10:49 AM, Jake Farrell > 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 next > > release candidate. Improving

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 API, but i don't see

Re: 0.10.0 Feature Requests

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 next release candidate. Improving our documentation and website should be an ongoing effort -Jake On Thu, Sep 10, 2015 at 1:43 PM, Zameer Manji wrote: >

Re: Testing our UI code

+1 to that, thanks for looking into this -Jake On Thu, Sep 10, 2015 at 12:20 PM, Joshua Cohen wrote: > Yes, it should be. I haven't actually verified it myself yet, but based on > the description of the gradle node.js plugin[1], it seems completely > painless: > > This plugin enables you to run

Re: [DRAFT] [REPORT] Apache Aurora

er all > the required points? > > On Tue, Sep 8, 2015 at 6:29 PM, Jake Farrell wrote: > >> 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

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 suggestions for edits pri

Re: Roadmap

ose ;). > > > > > > > > > > > > > > On Mon, Aug 31, 2015 at 9:32 PM, Bill Farner < > > terasur...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > >> I would love to see this come together! > > > > > > >>

Roadmap

In an initiative and make it easier for new people coming to Aurora to know where to get started and provide community contributions I would like to start a public roadmap (either a file within our repo or in jira) to make it easier for everyone to track releases and know what our goals are for eac

Re: [VOTE] Release Apache Aurora 0.9.0 debs

+1 to this set of packages for future votes/rc's on these packages we should script out the creation and addition of the subversion per rc,(like 0.9.0-1, 0.9.0-2, etc.), but not a blocker for this release -Jake On Sat, Aug 29, 2015 at 12:59 PM, Bill Farner wrote: > I propose that we accept the

Re: Forking twitter-commons into our tree

; Can the namespace rename be done in a follow up commit? Otherwise the > review/commit touches every single Java file and becomes very difficult to > understand. > > On Fri, Aug 21, 2015 at 8:08 AM, Jake Farrell wrote: > > > Since the IP has been donated to the ASF the namespace co

Re: Forking twitter-commons into our tree

Forking twitter-commons into our tree > > > > > To: > > > > > Cc: Jake Farrell > > > > > > > > > > > > > > > I'll see what I can do about IP clearance. > > > > > > > > > > For giggles, how much wor

Re: [PROPOSAL] Changes to the Python BUILD layout

+1 -Jake On Thu, Jul 30, 2015 at 7:24 PM, Kevin Sweeney 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 testing deployment with the >

Re: [PROPOSAL] Source releases vs artifact releases

o the released code which would warrant a new release candidate. -Jake On Mon, Jul 27, 2015 at 11:33 PM, Bill Farner wrote: > Wouldn't a separate repo make it even more difficult to associate build > script changes to source code changes? > > -=Bill > > On Mon, Jul 27, 2015 at

Re: [PROPOSAL] Source releases vs artifact releases

e release/vote. > > I've had several useful 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.

[RESULT][VOTE] Release Apache Aurora 0.9.0 RC0

All, The vote to accept Apache Aurora 0.9.0 RC0 as the official Apache Aurora 0.9.0 release has passed. +1 (Binding) -- Jake Farrell Bill Farner Kevin Sweeney Zameer Manji Brian Wickman +1 (Non-binding) -- Joshua Cohen +0

[VOTE] Release Apache Aurora 0.9.0 RC0

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

Re: Forking twitter-commons into our tree

, Jul 2, 2015 at 10:41 PM, Bill Farner 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 wrote: > > > no objections, but we would have to

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 wrote: > Hey, > > Aurora depends heavily on twitter-commons for lots of functionality. > However upstream is not ver

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 wrote: > All, > I have packaged up and staged

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 wrote: > It looks like there are checksums of the signatures, is that intentional? > > On Thu, Jun 11, 2015 at 1:31 PM, Jake Farrell wrote: > >> All, >> I have packaged up and s

[VOTE] Release Apache Aurora 0.8.0 API Artifacts

All, I have packaged up and staged the API jar/source artifacts from Apache Aurora 0.8.0 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.8.0 release artifacts. Aurora 0.8.0 API artifacts staging repo details inclu

[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 Aurora

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 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* > Date: Sunday, June 7,

Re: Heads up: Requiring java 8

This is a good first item to add to the NEWS file (if we are going to use a separate file for things like this) -Jake On Tue, May 12, 2015 at 11:21 AM, Bill Farner wrote: > Hello everyone, > > As previously agreed [1], we are transitioning to use Java 8 language > features, thus requiring a 1.8

[RESULT][VOTE] Release Apache Aurora 0.8.0 RC1

With 5 +1's (4 binding, 1 community) the vote to release Apache Aurora 0.8.0-rc1 as the official 0.8.0 release passes. Thanks to everyone that participated in contributing and validating this release -Jake On Fri, May 8, 2015 at 12:14 AM, Jake Farrell wrote: > All, > I propose tha

Re: Human-readable release notes

I would advocate for a second file to CHANGELOG, a NEWS file, which contains details on security issues, upgrade notes and any important tickets to call out in a given release. If a developer is working on a ticket and it meets any of this criteria then that file should be updated as part of the pa

[VOTE] Release Apache Aurora 0.8.0 RC1

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

[RESULT][VOTE] Release Apache Aurora 0.8.0 RC0

Due to the concerns with the changelog I am canceling the vote for rc0 and will start a new vote for rc1 once the patches are in place to address this issue -Jake On Mon, May 4, 2015 at 10:41 PM, Jake Farrell wrote: > All, > I propose that we accept the following release candidate

Re: [DRAFT][REPORT] Apache Aurora

PMC/Committership changes needs to have the dates for our last committer and PMC member added, other than that looks good -Jake On Thu, May 7, 2015 at 4:41 PM, Bill Farner wrote: > *Please find a draft of our board report below. Happy to discuss any > modifications anyone would like to see! I

Re: the status of pesos

ever becomes a > consistent story for the mesos github organization, we can reevaluate. > > Jake, what do we do about setting up these repositories? > > On Thu, Apr 23, 2015 at 7:14 PM, Jake Farrell wrote: > > > Creating a project on Github as suggested does not give the IP rights

Re: Review Request 33854: Fix RC verification script.

l Farner wrote: > > > > > --- > > This is an automatically generated e-mail. To reply, visit: > > https://reviews.apache.org/r/33854/ > > --- > > > > Review request for Aurora and Jake Far

[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.git&f=CHANGELOG&hb=0.8.0-rc0 The branch used to c

Re: the status of pesos

whatever, since aurora is taken), giving all committers write access to all > projects therein. We may not be able to rely upon reviewboard, but we can > at least solve the problem of ownership. > > Thoughts? > > > > > On Mon, Apr 20, 2015 at 7:29 PM, Jake Farrell wrote:

Re: the status of pesos

We only sync reviewboard repos from our git-wip or svn servers. I would recommend that we move them into aurora- name git repos so they can have their own release cycles -Jake On Mon, Apr 20, 2015 at 5:50 PM, Brian Wickman wrote: > I started work in r/32373

Re: [DRAFT][REPORT] Apache Aurora -

+1 -Jake On Mon, Apr 6, 2015 at 8:05 PM, Bill Farner wrote: > *Please find a draft of our board report below. Happy to discuss any > modifications anyone would like to see! I'll be submitting this tomorrow, > including any accepted edits.* > > > > ## Description: > > Aurora is a service sched

Re: Aurora JIRA permissions

+1, less restrictive for people interested in helping out -Jake On Thu, Apr 2, 2015 at 12:23 AM, Bill Farner wrote: > We've historically had trouble with people not being able to assign tickets > to themselves, which was caused by permissions restrictions. I've updated > the project permission

Graduation checklist

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

Graduation changes

As part of becoming a TLP our mailing lists have changed, everyone subscribed to the lists has been moved over, the new lists are the same as the old lists just missing the .incubator part now dev@aurora.apache.org Our website has also moved over to http://www.aurora.apache.org Our git and svn re