Team, Great progress is being made and the total number of JIRAs assigned to 1.0 is closing down. In JIRA, a 1.1 version has been setup so that as new items come in, that aren’t against the already active 1.0 goals, they can go there. I’ll go ahead and reassign new tickets that come in assigned to 1.0 to 1.1 as necessary. That way we can stay focused on the existing 1.0 JIRAs and any new JIRAs that arise that address 1.0 things.
As the tickets begin to wind down I will start a more formal RM process and give regular statuses of the lingering tickets like I did with 0.7.0. Also if able, please be building off of master and providing feedback of findings if they’re not already captured in a JIRA. Joe - - - - - - Joseph Percivall linkedin.com/in/Percivall e: [email protected] On Thursday, July 14, 2016 3:16 PM, Joe Witt <[email protected]> wrote: awesome joe thanks. Also, i think we should go through all current 1.0 tickets and encourage others to do so as well... On tickets which have migration implications and therefore need to be in the migration guide we should label them 'migration' and then ensure they have comments which explain the migration concern. Providing good documentation for those going from 0.x to 1.x will be essential to helping people make that transition. Thanks Joe On Tue, Jul 12, 2016 at 10:06 PM, Joe Percivall <[email protected]> wrote: > This is going to be an awesome release and I'm excited to see what others > think of all the great work that has gone into it. I would be more than happy > to act as the RM for the 1.0. I can start tomorrow looking through the > tickets assigned to 1.0 and help move them towards completion. > > Joe > - - - - - - > Joseph Percivall > linkedin.com/in/Percivall > e: [email protected] > > > > > On Tuesday, July 12, 2016 12:14 PM, Joe Witt <[email protected]> wrote: > Team, > > There has been a lot of progress for 1.0 and with 0.7 in the final > phases and the first minifi release in the mirror its time to start > pulling 1.0 together. There are a fairly large number of outstanding > tickets most of which are there from 'back in the day' marking things > as a '1.0' fix version meaning 'the future' or habits of making > tickets and preassigning fix releases even though they're not being > worked just yet. So cleaning a lot of JIRA stuff up but it looks like > we can start working the RC process fairly soon. > > Important remaining finishing touch work is underway. Of the > remaining 1.0 tickets an important push is to cleanup deprecated > things and leverage Apache Yetus annotations to very clearly > articulate API intent/stability/openness. For those building on > Apache NiFi it means they'll have better clarity on what is subject to > change and not and for those building Apache NiFi itself it means we > will have more flexibility to change parts of the system which are not > considered public API. There are a couple really exciting roadmap > items like extension/template registry that Matt/Puspendu have been > discussing lately which will also be a tremendous help for agility > with extensions too. Other things like variable registry will be key > for that too. > > This 1.0 release for those following along the master branch and > associated JIRAs has some really cool updates in it. For example, > NiFi will now be able to support multiple editors in parallel without > the dreaded "too late you must refresh". It supports fine grained > authorization logic rather than coarse grained 'system wide' DFM or > Read-Only which makes multiple teams working on the same system have a > far better operational capability. The UI has been refreshed/updated > and provides a more responsive and effective basis to evolve from. > > I'm happy to take on the RM work for the release but if someone else > wants to take a stab at it please advise. > > Thanks! > Joe
