All,
Just submitted the INFRA request for a confluence wiki space:
https://issues.apache.org/jira/browse/INFRA-9695
Sean already has a good ticket or two in to get a contribution guide going:
https://issues.apache.org/jira/browse/NIFI-359
https://issues.apache.org/jira/browse/NIFI-358
As far as 'build process' improvements go during the 010 release
process we restructured some of the build to support better builds,
DRY, easier RAT and checkstyle enforcement. This release cycle for
'build process' improvements we can focus on documenting how to
contribute. I will make these my priority
In addition Andrew is absolutely right that we must get the upgrade
process for such a release properly documented:
https://issues.apache.org/jira/browse/NIFI-628
However, please keep this thread going to help ensure Andrew is good
to go and lets use this to better inform what we should include in the
guide. Andrew if you run into any curveballs we've not mentioned
please advise.
Thanks
Joe
On Fri, May 22, 2015 at 3:35 PM, <[email protected]> wrote:
> There is existing wiki-ness at Apache and each project has access to it.
>
> A
>
> Sent from my iPhone
>
>> On May 22, 2015, at 2:03 PM, Andrew Hulbert <[email protected]> wrote:
>>
>> +1 for the wiki (i tried to actually search earlier). Does ASF provide a
>> wiki? Generally moving between semantic major/minor versions I like to look
>> for some text telling me what changed/how I'm going to break it.
>>
>> Since my flows are mainly data moving and not too much reporting at the
>> moment other than ActivityMonitors and error emails I think it should work
>> OK.
>>
>> The next thing I'm going to dig into are summary emails/graphs (e.g. flow
>> rates from sources per hour/day/week). I assume someone is already doing
>> this? I saw ganglia integration but I admit I haven't read through
>> everything yet. Working on it.
>>
>> Thanks for the help!
>>
>> Andrew
>>
>>> On 05/22/2015 12:09 PM, Joe Witt wrote:
>>> This feels like a really good example of us needing a wiki now.
>>>
>>>> On Fri, May 22, 2015 at 11:49 AM, Mark Payne <[email protected]> wrote:
>>>> Andrew,
>>>>
>>>> In addition, if you have any Controller Services or Reporting Tasks
>>>> defined in 0.0.2 (conf/reporting-tasks.xml and
>>>> conf/controller-services.xml), those will not be loaded in 0.1.0. We have
>>>> done this in order to move those components into the UI and make them
>>>> first-class citizens. Those are now configured in the UI's Settings page.
>>>>
>>>> Thanks
>>>> -Mark
>>>>
>>>> ________________________________
>>>>> Date: Fri, 22 May 2015 11:42:50 -0400
>>>>> Subject: Re: Upgrading from 0.0.2 to 0.1.0 and stat processor
>>>>> From: [email protected]
>>>>> To: [email protected]
>>>>>
>>>>> Hello Andrew,
>>>>> It might be helpful to take a look at the System Properties section of
>>>>> the Admin Guide [1] if you haven't already. We address some tips for
>>>>> upgrading there. You are correct, though, that we should try to give a
>>>>> heads-up whenever we distribute a new release -- if there are any
>>>>> implications for upgrading. In general, as noted at the following link,
>>>>> you definitely want to look at the nifi.properties file to make sure
>>>>> there aren't any additions/deletions just in case. (But we should
>>>>> really tell people about such changes if they exist!)
>>>>>
>>>>> [1]
>>>>> https://nifi.incubator.apache.org/docs/administration-guide.html#system_properties
>>>>>
>>>>> Cheers,
>>>>> Jenn
>>>>>
>>>>> On Fri, May 22, 2015 at 11:23 AM, Andrew Hulbert
>>>>> <[email protected]<mailto:[email protected]>> wrote:
>>>>> Hi folks,
>>>>>
>>>>> Is there anything I need to know for upgrading from 0.0.2 to 0.1.0?
>>>>>
>>>>> I assuming I only need to copy my flow conf XML file to the new untar'd
>>>>> distribution and restart but I wanted to check. I already let things
>>>>> drain out.
>>>>>
>>>>> I think it may be useful to have a "upgrading" section with each
>>>>> release and I'd be happy to contribute that somewhere if you have an
>>>>> idea!
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Andrew
>>
