Sounds good. I’ll prepare a release candidate and as I mentioned in another thread use the opportunity to document the release process.
-Taylor > On Jan 27, 2017, at 10:41 AM, Bobby Evans <[email protected]> wrote: > > I am +1 on a release of 1.0.3 > > > - Bobby > > On Wednesday, January 25, 2017, 4:25:06 AM CST, Jungtaek Lim > <[email protected]> wrote:Bump. Any other opinions? I got two non-binding +1 > but also would like to > see PMCs opinions. > > And I also would like to volunteer the release manager on this version. Our > documentation doesn't describe the release process, which is another > blocker for me to be release manager. > > - Jungtaek Lim (HeartSaVioR) > > 2017년 1월 20일 (금) 오후 7:20, Alexandre Vermeerbergen <[email protected]>님이 > 작성: > >> +1 from me (non-binding) >> >> 2017-01-20 5:36 GMT+01:00 Jungtaek Lim <[email protected]>: >> >>> Hi devs, >>> >>> While we're working on issues targeted for 1.1.0, remaining issues on >> 1.1.0 >>> epic are not relevant to 1.0.3. Since we also have lots of resolved >> issues >>> for 1.0.3 [1 < >> https://github.com/apache/storm/blob/master/CHANGELOG.md#103 >>>> ], >>> I think it would be better to start release process for 1.0.3 separately, >>> not waiting on work done for 1.1.0. >>> >>> What do you think? >>> >>> Thanks, >>> Jungtaek Lim (HeartSaVioR) >>> >>> [1] https://github.com/apache/storm/blob/master/CHANGELOG.md#103 >>>
