Re: [DISCUSS] Closing in on a 0.x release

Okay, then, let's proceed with Joe S. as RM for 0.7.1. On Wed, Oct 12, 2016 at 9:42 PM, Joe Witt wrote: > As long as someone has commit privileges they can certainly step up to > take on release management. The only special bit in a release beyond > commit privileges is

Re: [DISCUSS] Closing in on a 0.x release

As long as someone has commit privileges they can certainly step up to take on release management. The only special bit in a release beyond commit privileges is needing sufficient binding votes. Thanks Joe for offering to take that on. Joe On Wed, Oct 12, 2016 at 9:24 PM, Aldrin Piri

Re: [DISCUSS] Closing in on a 0.x release

It is also my belief that we have not had anyone but PMC members perform the release process. Certainly no objections here and, as mentioned in the link, still requires the same PMC validation. I've seen this occur in some other ASF projects as well and certainly is beneficial to our community to

Re: [DISCUSS] Closing in on a 0.x release

Does anyone object to Joe Skora being release manager for 0.7.1? Based on this [1] I don't see any reason he shouldn't be able to. I've offered out of band to assist. 1. http://www.apache.org/dev/release-publishing.html#release_manager On Wed, Oct 12, 2016 at 4:15 PM, Tony Kurc

Re: [DISCUSS] Closing in on a 0.x release

I'm willing take a try at RM or work with someone to understand it in the future. On Tue, Oct 11, 2016 at 3:50 PM, Tony Kurc wrote: > Awesome. I propose we start building a release candidate off of > 40618364e70a966f9c1e425674b53b22b1fb0fb0 soon. > > I believe I was the sole

Re: [DISCUSS] Closing in on a 0.x release

Awesome. I propose we start building a release candidate off of 40618364e70a966f9c1e425674b53b22b1fb0fb0 soon. I believe I was the sole volunteer to RM, and unless I hear otherwise, I presume I will be doing so. I'd like to give the commit at least a good 24 hours for some people to bang on it

Re: [DISCUSS] Closing in on a 0.x release

NIFI-2774 is now complete and merged to both master and 0.x branches. +1 on a release from the 0.x branch now. -- Mike On Mon, Oct 10, 2016 at 10:24 AM, Michael Moser wrote: > I feel that Oleg was really close, and it would be nice for this to be in > 0.7.1 but it isn't

Re: [DISCUSS] Closing in on a 0.x release

I feel that Oleg was really close, and it would be nice for this to be in 0.7.1 but it isn't necessary. I did functional testing on the current state of the PR and I am +1 in that respect. -- Mike On Oct 10, 2016 9:40 AM, "Tony Kurc" wrote: > So in reviewing the Jiras, it

Re: [DISCUSS] Closing in on a 0.x release

So in reviewing the Jiras, it looks like the two tickets NIFI-2429, NIFI-2874 were merged in and NIFI-2774 is still under discussion. Oleg, Mike, are we feeling like we're close, or would this best fit in the next 0.x release? Tony On Fri, Oct 7, 2016 at 3:21 PM, Michael Moser

Re: [DISCUSS] Closing in on a 0.x release

Thanks Joe Witt, I reviewed that PR and got it into 0.x. Since we decided that our next 0.x release will be 0.7.1, I am going through JIRA and for all Resolved tickets marked against 0.8.0 I am changing their Fix Version to 0.7.1. Open tickets I will not change. -- Mike On Fri, Oct 7, 2016 at

Re: [DISCUSS] Closing in on a 0.x release

Team, Mark Payne just opened this one: https://issues.apache.org/jira/browse/NIFI-2874 It should probably be in this release if able. Thanks Joe On Mon, Oct 3, 2016 at 10:48 AM, Michael Moser wrote: > I am reviewing the PR for NIFI-2774 ConsumeJMS and we need someone to >

Re: [DISCUSS] Closing in on a 0.x release

I am reviewing the PR for NIFI-2774 ConsumeJMS and we need someone to review the PR for NIFI-2429 PersistentProvenanceRepository. Once those are complete I think we can start the process to cut 0.7.1. -- Mike On Mon, Oct 3, 2016 at 9:49 AM, Tony Kurc wrote: > So, sounds like

Re: [DISCUSS] Closing in on a 0.x release

So, sounds like we have enough support to go ahead. How are we feeling about what our timeline should be on this? On Wed, Sep 28, 2016 at 11:14 PM, Joe Witt wrote: > +1 to an 0.7.1 with the bugs that have been addressed already. > Even bigger +1 to Tony volunteering as RM!

Re: [DISCUSS] Closing in on a 0.x release

+1 to an 0.7.1 with the bugs that have been addressed already. Even bigger +1 to Tony volunteering as RM! Thanks Joe On Tue, Sep 27, 2016 at 10:24 PM, Brandon DeVries wrote: > I agree sooner rather than later for cutting 0.7.1. I think Mike's question > to some degree was whether

Re: [DISCUSS] Closing in on a 0.x release

I agree sooner rather than later for cutting 0.7.1. I think Mike's question to some degree was whether or not some of those tickets were worth fixing in 0.x. For example, I'm not sure how much I care about: NIFI-2571 deprecate NiFiProperties.getInstance() NIFI-2163 nifi.sh follow the Linux

Re: [DISCUSS] Closing in on a 0.x release

I think I brought this up before, I sort of expected we may do more 0.x releases. I certainly think the more the bugs we can fix, the merrier, and it seems like your list is a good initial strawman for a bug fix release of we collectively would like to put one together. While the tickets with

[DISCUSS] Closing in on a 0.x release

All, I would like to start the discussion of making the next official release of the 0.x branch. I propose that this release be numbered 0.7.1 since it seems that only bug fixes have occurred on the 0.x branch since 0.7.0 was released. The JIRA link [1] below can show you the tickets that have