Adam,
I have created this Jira ticket for you:
https://issues.apache.org/jira/browse/OFBIZ-5712with all the fields already set.
It would be great if you could edit the summary/description with the relevant changes you did/are doing and then just resolve it. This will then be automatically included in the release notes for the next branch release.
Thanks,
Jacopo
On Aug 13, 2014, at 10:21 PM, Jacques Le Roux <
[hidden email]> wrote:
> You can still create a Jira issue and select the concerned versions
>
> Jacques
>
> Le 13/08/2014 21:54, Adam Heath a écrit :
>> On 08/10/2014 08:19 AM, Jacques Le Roux wrote:
>>> As mentioned Jacopo, the Jira issue creation can be done after, even by another person.
>>> The point is to collect changes by versions (releases)
>>>
>>> Jacques
>>>
>>> Le 10/08/2014 14:14, Jacques Le Roux a écrit :
>>>> Also I forgot to mention (again) that, with our new policy to automatically grab new features or bug fixes from Jira, a direct commit should not happen for major new features or bug fixes.
>>>> We shall first create a Jira issue, even we you don't submit a patch (which is preferable for peers reviews), in order to fill the version to allow creating reports like
>>>>
https://issues.apache.org/jira/browse/OFBIZ/fixforversion/12327361/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel>>>>
>>
>> Oops, missed this, my bad, on my recent parallelization changes.
>>
>> ps: I really wish that there was some kind of git-based workflow.
>>
>>
>>