+1 for both, leave ticket open and tag it with label "backport-needed" .
-- Thanks & Regards --- Arun Patidar Manager, Enterprise Software Development HotWax Systems Pvt Ltd.www.hotwaxsystems.com On Tue, Jul 11, 2017 at 12:57 PM, gil portenseigne < gil.portensei...@nereide.fr> wrote: > +1 > > Got the same Opinion > > Regards > > Gil > > > > On 11/07/2017 08:38, Pranay Pandey wrote: > >> +1 >> >> I think committer of the fix in trunk should take the ownership of >> backporting. If you are not able to do it now, keep it open. Tagging the >> ticket is a good idea. Bulk backporting should be avoided as it's error >> prone. >> >> Best regards, >> Pranay Pandey >> www.hotwaxsystems.com >> www.hotwax.co >> >> On Mon, Jul 10, 2017 at 5:32 PM, Michael Brohl <michael.br...@ecomify.de> >> wrote: >> >> Hi everyone, >>> >>> I think we should setup some kind of policy for the bugfixing in the >>> project. >>> >>> While every committer is free to decide if he does a backport himself, we >>> should make sure that bugfixes go into the supported release branches >>> also. >>> >>> I propose to define the following policies: >>> >>> 1. bugfixes should be backported by the committer who does the bugfix in >>> trunk if possible >>> >>> 2. if he does not, for an reason, backport the bugfix, he should either >>> open a new Jira for a task to backport or leave the original issue open >>> with a remark that a backport is needed. >>> >>> (I tend to leave the issue open). >>> >>> In no case should we close a Jira issue without doing 1. or 2. >>> >>> What do you think? >>> >>> Regards, >>> >>> Michael Brohl >>> ecomify GmbH >>> www.ecomify.de >>> >>> >>> Am 10.07.17 um 13:26 schrieb Jacques Le Roux (JIRA): >>> >>> [ https://issues.apache.org/jira/browse/OFBIZ-9459?page=com. >>>> atlassian.jira.plugin.system.issuetabpanels:comment-tabpane >>>> l&focusedCommentId=16080188#comment-16080188 ] >>>> >>>> Jacques Le Roux commented on OFBIZ-9459: >>>> ---------------------------------------- >>>> >>>> Hi Arun, I noticed that, like few other issues (at least OFBIZ-9473, >>>> OFBIZ-9316, OFBIZ-9317) that you did not backport this bug. Is there a >>>> reason? Do you want me to do it? Thanks. >>>> >>>> Wrong screen redirection after adding note on Lead profile screen >>>> >>>>> ----------------------------------------------------------------- >>>>> >>>>> Key: OFBIZ-9459 >>>>> URL: https://issues.apache.org/jira >>>>> /browse/OFBIZ-9459 >>>>> Project: OFBiz >>>>> Issue Type: Bug >>>>> Components: marketing >>>>> Reporter: Jagpreet Kaur >>>>> Assignee: Arun Patidar >>>>> Fix For: Upcoming Release >>>>> >>>>> Attachments: Create Note.png, OFBIZ-9459.patch, >>>>> Screenredirection.png >>>>> >>>>> >>>>> 1) Go to SFA component. >>>>> 2) Click on Leads tab [https://demo-trunk-ofbiz.apac >>>>> he.org:8443/sfa/control/FindLeads|https://demo-trunk-ofbiz >>>>> <http://he.org:8443/sfa/control/FindLeads%7Chttps://demo-trunk-ofbiz>. >>>>> apache.org:8443/sfa/control/FindLeads]. >>>>> 3) Choose any partyId from All Lead list, you will be navigated to Lead >>>>> profile. [https://demo-trunk-ofbiz.apache.org:8443/sfa/control/viewpr >>>>> ofile?roleTypeId=LEAD&partyId=DemoLead|https://demo-trunk- >>>>> ofbiz.apache.org:8443/sfa/control/viewprofile?roleTypeId >>>>> =LEAD&partyId=DemoLead] >>>>> 4) Click on "Create New" button in the Notes section. >>>>> 5) Add the Note content. >>>>> 6) Click on "Save Button". >>>>> View redirection should be profile but it shows the blank screen. >>>>> >>>>> >>>> -- >>>> This message was sent by Atlassian JIRA >>>> (v6.4.14#64029) >>>> >>>> >>> >>> >
