Summary of IRC Meeting in #aurora at Mon Sep 15 18:02:49 2014: Attendees: davmclau, wickman, jfarrell, mchucarroll, wfarner, jcohen, Yasumoto, kts, jaybuff, mkhutornenko, zmanji, dlester, kacieee
- Preface - New release - Action: publish 0.6.0 release candidate - Action: make standalone aurora v2 client default for 0.6.0 release - Action: mchucarroll & jcohen to investigate if AUROROA-677 needs to be resolved to make aurora v2 client default - Action: mchucarroll to clean up client docs for v2 default - Action: davmclau and mchucarroll to add KEYS entries - Action: jfarrell to add note on KEYS entries to committers.md - Action: document upgrade path 0.5.0 to 0.6.0 - shiro IRC log follows: ## Preface ## [Mon Sep 15 18:03:09 2014] <kts>: good morning everyone, let's get started with a quick roll call [Mon Sep 15 18:03:13 2014] <wfarner>: here [Mon Sep 15 18:03:19 2014] <mchucarroll>: hiya [Mon Sep 15 18:03:21 2014] <Yasumoto>: howdy [Mon Sep 15 18:03:29 2014] <davmclau>: here [Mon Sep 15 18:03:32 2014] <zmanji>: here [Mon Sep 15 18:03:37 2014] <dlester>: present [Mon Sep 15 18:03:44 2014] <mkhutornenko>: here [Mon Sep 15 18:03:53 2014] <wickman>: here [Mon Sep 15 18:04:26 2014] <jcohen>: here [Mon Sep 15 18:04:45 2014] <kts>: great, let's get started [Mon Sep 15 18:05:05 2014] <kts>: does anyone have any agenda items? [Mon Sep 15 18:05:41 2014] <davmclau>: The subject of the next release came up in IRC last week. [Mon Sep 15 18:06:02 2014] <davmclau>: Given that the current release has a couple of bad bugs in it, it might be worth cutting a new one. [Mon Sep 15 18:06:56 2014] <zmanji>: Do we have a list of what we want in the next release? [Mon Sep 15 18:07:37 2014] <kts>: we've been using the Fix Version jira attribute (sparingly it seems) [Mon Sep 15 18:08:18 2014] <dlester>: should we set the #topic to release? ## New release ## [Mon Sep 15 18:09:52 2014] <kts>: % git diff --shortstat 0.5.0-rc2 master [Mon Sep 15 18:09:53 2014] <kts>: 279 files changed, 15072 insertions(+), 4527 deletions(-) [Mon Sep 15 18:10:38 2014] <dlester>: sounds like a good time for another release [Mon Sep 15 18:10:54 2014] <kts>: do we have any volunteers for release manager? [Mon Sep 15 18:12:20 2014] <jaybuff>: bhuvan might be up for coordinating it [Mon Sep 15 18:12:24 2014] <wfarner>: IIRC jfarrell suggested we cut a new release in sync with an upcoming feature - the job updater work [Mon Sep 15 18:12:31 2014] <jaybuff>: bhuvan: yt? [Mon Sep 15 18:12:57 2014] <wfarner>: this is probably timed fairly well, as remaining code should land this week [Mon Sep 15 18:13:09 2014] <jfarrell>: wfarner: yeah, think thats a good milestone to shoot for [Mon Sep 15 18:13:37 2014] <jaybuff>: could the aurora v2 client be made the default client? or is it already? [Mon Sep 15 18:14:01 2014] <zmanji>: @jaybuff: Iâve been talking about killing the v1 client but nothing concrete has been set yet. [Mon Sep 15 18:14:12 2014] <zmanji>: I would like to remove the v1 client for the next release. [Mon Sep 15 18:14:19 2014] <Yasumoto>: that'd also be a good cutover for this next release [Mon Sep 15 18:14:20 2014] <mchucarroll>: In the open-source, we can definitely kill the v1. [Mon Sep 15 18:14:28 2014] <Yasumoto>: s/cutover/feature [Mon Sep 15 18:14:39 2014] <mchucarroll>: Twitter folks will probably take longer to switch over. [Mon Sep 15 18:15:02 2014] <Yasumoto>: that should be okay- organizations can move at their own pace if we do it right [Mon Sep 15 18:15:05 2014] <mchucarroll>: We already have a standalone v2 target, and an end-to-end test. [Mon Sep 15 18:15:40 2014] <mchucarroll>: And weâre already issuing deprecation warnings to people who use v1 commands. So flipping over the default will be easy. [Mon Sep 15 18:15:43 2014] <jaybuff>: i dont see an advantage to killing it. just make v2 the default [Mon Sep 15 18:16:03 2014] <jaybuff>: right now /usr/bin/aurora == v1 and /usr/bin/aurora2 == v2? [Mon Sep 15 18:16:24 2014] <mchucarroll>: Yes - and aurora2 is actually a bridged binary that contains both v1 and v2. [Mon Sep 15 18:16:26 2014] <jfarrell>: kts: i'm happy to stand in for RM, but would prefer someone new (*wfarner*) to walk through the process and iron out any edge cases we might have missed in the first round [Mon Sep 15 18:16:54 2014] <mchucarroll>: Thatâs what I meant about âkillingâ v1 - removing it from the v2 executable, and making v2 the default. V1 can still be there as a different command. [Mon Sep 15 18:17:23 2014] <jaybuff>: mchucarroll: do you want the bridge to be the default or the standalone? [Mon Sep 15 18:17:42 2014] <jcohen>: We should probably fix https://issues.apache.org/jira/browse/AURORA-677 before declaring v2 the default? [Mon Sep 15 18:17:46 2014] <mchucarroll>: Standalone. [Mon Sep 15 18:17:53 2014] <jcohen>: test_end_to_end_v2.sh fails on config list [Mon Sep 15 18:18:12 2014] <jaybuff>: aurora-677 [Mon Sep 15 18:18:38 2014] <mchucarroll>: (I think that 677 is a vagrant issue; but we can discuss that offline.) [Mon Sep 15 18:20:05 2014] <jaybuff>: are we going to call this release 0.6.0? [Mon Sep 15 18:20:08 2014] <kts>: so that sounds like a good 0.6.0 target feature [Mon Sep 15 18:20:18 2014] <jfarrell>: yes, should be 0.6.0 [Mon Sep 15 18:20:21 2014] <jaybuff>: #action publish 0.6.0 release candidate [Mon Sep 15 18:20:38 2014] <jaybuff>: #action make standalone aurora v2 client default for 0.6.0 release [Mon Sep 15 18:20:41 2014] <jaybuff>: #action mchucarroll & jcohen to investigate if AUROROA-677 needs to be resolved to make aurora v2 client default [Mon Sep 15 18:21:13 2014] <kts>: jaybuff: sounds like wfarner wants to hold off until the server-side updater is committed [Mon Sep 15 18:21:14 2014] <jfarrell>: lets create a 0.6.0 rc ticket and link all subtasks there to make tracking easier [Mon Sep 15 18:21:32 2014] <jaybuff>: +1 [Mon Sep 15 18:21:34 2014] <kts>: +1 [Mon Sep 15 18:22:18 2014] <kts>: wfarner or davmclau any interest in being release manager for 0.6.0? [Mon Sep 15 18:22:47 2014] <kts>: jaybuff: release manager has to be a committer I think, but we'd definitely appreciate bhuvan's assistance [Mon Sep 15 18:23:16 2014] <jaybuff>: if we're going to make v2 default the docs need to be cleaned up [Mon Sep 15 18:23:33 2014] <davmclau>: I'd like to know what is involved in being a release manager before volunteering :) [Mon Sep 15 18:23:39 2014] <mchucarroll>: Yeah, Iâll do the docs. [Mon Sep 15 18:23:51 2014] <jaybuff>: mchucarroll: thanks, i'll open a "make v2 client default" jira [Mon Sep 15 18:23:51 2014] <mchucarroll>: #action mchucarroll to clean up client docs for v2 default [Mon Sep 15 18:24:41 2014] <kts>: davmclau: print preview says it's only 17 pages - http://incubator.apache.org/guides/releasemanagement.html [Mon Sep 15 18:25:01 2014] <jfarrell>: yes, the way our scripts run the rm has to be a committer, currently limited to one of [kts, wfarner, wickman, maxim, jfarrell ] [Mon Sep 15 18:25:25 2014] <kts>: jfarrell: and davmclau right? [Mon Sep 15 18:25:58 2014] <jcohen>: mchucarroll is a committer as well [Mon Sep 15 18:26:24 2014] <jfarrell>: both missing KEYS file entries [Mon Sep 15 18:26:50 2014] <kts>: #action davmclau and mchucarroll to add KEYS entries [Mon Sep 15 18:27:32 2014] <jfarrell>: i'll update the committer guide to make that an onboarding item if its missing (dont recall if its there or not) [Mon Sep 15 18:28:13 2014] <kts>: the release process is documented at https://github.com/apache/incubator-aurora/blob/master/docs/committers.md#creating-a-release [Mon Sep 15 18:29:03 2014] <kts>: #action jfarrell to add note on KEYS entries to committers.md [Mon Sep 15 18:30:06 2014] <jfarrell>: 0.6.0 release candidate tracking ticket is AURORA-711 [Mon Sep 15 18:31:10 2014] <kts>: aurora-704 is one other piece of documentation that should be in 0.6.0 [Mon Sep 15 18:31:38 2014] <wickman>: also AURORA-703 [Mon Sep 15 18:31:44 2014] <kts>: aurora-704 [Mon Sep 15 18:31:51 2014] <kts>: aurora-703 [Mon Sep 15 18:32:28 2014] <kts>: so the major features of 0.6.0 will be pure-v2 client, server-side updates, and documentation [Mon Sep 15 18:32:29 2014] <jaybuff>: if someone could just do a quick explaination in the jira for 703 it'd save me a ton of time [Mon Sep 15 18:32:41 2014] <jaybuff>: kts: +1 [Mon Sep 15 18:32:45 2014] <kts>: does that sound good to everyone? [Mon Sep 15 18:32:54 2014] <wfarner>: +1 [Mon Sep 15 18:33:14 2014] <jfarrell>: +1 [Mon Sep 15 18:34:17 2014] <davmclau>: +1 [Mon Sep 15 18:34:36 2014] <jcohen>: +1 [Mon Sep 15 18:34:41 2014] <mchucarroll>: ++ [Mon Sep 15 18:36:14 2014] <kts>: great! so... any volunteers for release manager? [Mon Sep 15 18:39:30 2014] <jcohen>: one question on the release, do we use semver for versioning? and if so, are any of the proposed changes considered breaking? Async updates seems like a major change... [Mon Sep 15 18:39:56 2014] <jfarrell>: jcohen: yes, we use semver [Mon Sep 15 18:40:42 2014] <mchucarroll>: but I believe that async wonât be a breaking change - I think at least initially, weâre going to keep the current update, and use the async as an option. [Mon Sep 15 18:41:06 2014] <jcohen>: ok [Mon Sep 15 18:41:08 2014] <kts>: Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable. [Mon Sep 15 18:44:25 2014] <wickman>: it also depends on what you consider the 'api' here -- if the api is the client, it will not be a breaking change. [Mon Sep 15 18:46:48 2014] <kacieee>: I'd like to become a mentor on this project for the outreach program for women, how do I go about this? [Mon Sep 15 18:47:03 2014] <wfarner>: yeah, i wouldn't consider updates warranting any semver flagging [Mon Sep 15 18:47:52 2014] <wfarner>: kacieee: awesome! can you reach out to dles...@twitter.com? [Mon Sep 15 18:48:05 2014] <wfarner>: he's leading that front for us [Mon Sep 15 18:48:27 2014] <kts>: regardless there'll definitely be an upgrade path 0.5.0 to 0.6.0 so we should be fine doing a minor version increment [Mon Sep 15 18:48:42 2014] <kts>: #action document upgrade path 0.5.0 to 0.6.0 [Mon Sep 15 18:49:22 2014] <kts>: does anybody have any other topics? [Mon Sep 15 18:49:37 2014] <kts>: we can check in next week and select a release manager then [Mon Sep 15 18:51:13 2014] <kts>: oh, one more thing ## shiro ## [Mon Sep 15 18:52:00 2014] <kts>: I've investigated shiro and written up a migration plan for it, I'll share with the list for comments in a bit [Mon Sep 15 18:52:11 2014] <kts>: ASFBot: meeting end [Mon Sep 15 18:52:25 2014] <wickman>: jay: i also just filed AURORA-708 which is a possible solution to the issue you mention [Mon Sep 15 18:52:28 2014] <wfarner>: ASFBot: meeting stop Meeting ended at Mon Sep 15 18:52:28 2014
