Commits and especially backports suggest best practice

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Commits and especially backports suggest best practice

Jacques Le Roux
Administrator
Hi,

I understand that every committer is free to commit and backport or not, but I'd like to propose a best practice.
When you backport something, if you know that it should not be backported in older releases, please pass the information. It makes reviewers task much
easier.
I put a note at
https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities#OFBizCommittersRolesandResponsibilities-Howshouldcommittershandlebackporting?

Thanks

Jacques

Reply | Threaded
Open this post in threaded view
|

Re: Commits and especially backports suggest best practice

Pranay Pandey-3
Makes perfect sense.

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Fri, Jun 10, 2016 at 1:18 AM, Jacques Le Roux <
[hidden email]> wrote:

> Hi,
>
> I understand that every committer is free to commit and backport or not,
> but I'd like to propose a best practice.
> When you backport something, if you know that it should not be backported
> in older releases, please pass the information. It makes reviewers task
> much easier.
> I put a note at
> https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities#OFBizCommittersRolesandResponsibilities-Howshouldcommittershandlebackporting
> ?
>
> Thanks
>
> Jacques
>
>