Jenkins build is back to normal : aurora-packaging-nightly #180

See

Re: Rollback Testing

Yes. Our nightly packaging builds take advantage of this. On Mon, Feb 1, 2016 at 2:27 PM, Joshua Cohen wrote: > I know the blocker for e2e tests in CI previously was the ability to run > vagrant. Is running docker from CI doable today? > > On Mon, Feb 1, 2016 at 2:40 PM, Bill Farner wrote: > >

Re: Deprecation Cycles

+1 to max(1 release, 90 days) On Mon, Feb 1, 2016 at 2:26 PM, Joshua Cohen wrote: > I'd propose the following: fields will be removed no less than 90 days and > 1 release after they have been deprecated. This might be a little bit > conservative w.r.t to days, so feel free to push back if you th

Re: Rollback Testing

I know the blocker for e2e tests in CI previously was the ability to run vagrant. Is running docker from CI doable today? On Mon, Feb 1, 2016 at 2:40 PM, Bill Farner wrote: > Definitely a nice thing to have, the big uncertainty will be whether anyone > cares enough to see the effort through. > >

Re: Deprecation Cycles

I'd propose the following: fields will be removed no less than 90 days and 1 release after they have been deprecated. This might be a little bit conservative w.r.t to days, so feel free to push back if you think, e.g., 60 days is more reasonable. On Mon, Feb 1, 2016 at 2:35 PM, Bill Farner wrote:

Re: Allow dots and hyphens in metric names

+1 On Wed, Jan 27, 2016 at 3:35 PM, Erb, Stephan wrote: > Bill suggested that I send a note here regarding a planned change of valid > metric names: https://reviews.apache.org/r/42879. Goal is to allow any > character that may be part of a user-defined job name, in particular dots > and hyphens.

Re: Rollback Testing

Definitely a nice thing to have, the big uncertainty will be whether anyone cares enough to see the effort through. e2e tests in jenkins can be done, but likely only if e2e tests start using docker instead of vagrant. I am supportive of both, but cannot personally invest the time at the moment.

Re: Deprecation Cycles

Sounds reasonable. Can you firm up the proposal and apply numbers? On Mon, Feb 1, 2016 at 12:09 PM, Joshua Cohen wrote: > This came up briefly last week, and we also discussed in the IRC meeting > today. Given the increased release cadence, I think we would benefit from > moving from release-ba

Rollback Testing

Another topic that came up today's IRC meeting was possibly adding some sort of automated rollback testing between builds. This is related to https://issues.apache.org/jira/browse/AURORA-1603 which was caused by an inability to rollback to an earlier commit after discovering https://issues.apache.o

Deprecation Cycles

This came up briefly last week, and we also discussed in the IRC meeting today. Given the increased release cadence, I think we would benefit from moving from release-based deprecation to time-based. That is to say, instead of deprecating in release X and removing release X+1, we would deprecate in

Summary of IRC Meeting in #aurora

Summary of IRC Meeting in #aurora at Mon Feb 1 19:06:57 2016: Attendees: mkhutornenko, adeshmukh, zmanji, benley, jcohen - Preface - Deprecation cycles - Action: jcohen to follow up w/ dev thread re: changing deprecation policy. - AURORA-1603 - Rollback testing - Action: jcohen to email dev@