Jira and releases change logs
Locked
Jira and releases change logs
 
Administrator
|
Hi Committers,
Please take the time to correctly fill the different Jira fields we now use for our releases change logs. For instance for in * Improvement:s use either Done or Implemented Status as you feel right * New features: use either Implemented Status * Bug: use the Fixed Status Don't forget to fill the Fix version/s field according to your changes. Notably, use Upcoming Branch and not trunk there. Also, even if when the svn commits comments are correctly done with a reference to the Jira issue number we can then get to the commits in Fisheye from the Development section of the Jira issue, I'd still recommend to put the commits references in a comment. It's always handy, and insures we have those references at hand even if the commits comments don't contain the Jira issue reference. Thanks for all the good work :) Jacques |
Re: Jira and releases change logs
|
Ok Jacques,
I propose to complete the page https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities with your sensible remarks ! I will do that tomorrow. Nicolas Le 17/12/2014 15:29, Jacques Le Roux a écrit : > Hi Committers, > > Please take the time to correctly fill the different Jira fields we > now use for our releases change logs. > > For instance for in > * Improvement:s use either Done or Implemented Status as you feel right > * New features: use either Implemented Status > * Bug: use the Fixed Status > > Don't forget to fill the Fix version/s field according to your > changes. Notably, use Upcoming Branch and not trunk there. > > Also, even if when the svn commits comments are correctly done with a > reference to the Jira issue number we can then get to the commits in > Fisheye from the Development section of the Jira issue, I'd still > recommend to put the commits references in a comment. It's always > handy, and insures we have those references at hand even if the > commits comments don't contain the Jira issue reference. > > Thanks for all the good work :) > > Jacques |
Re: Jira and releases change logs
|
|
+1
Thanks, Pranay Pandey Senior Manager, Enterprise Software Development HotWax Media www.hotwaxmedia.com On Thu, Dec 18, 2014 at 4:50 AM, Nicolas Malin <[hidden email]> wrote: > > Ok Jacques, > > I propose to complete the page https://cwiki.apache.org/ > confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities > with your sensible remarks ! > I will do that tomorrow. > > Nicolas > > Le 17/12/2014 15:29, Jacques Le Roux a écrit : > > Hi Committers, >> >> Please take the time to correctly fill the different Jira fields we now >> use for our releases change logs. >> >> For instance for in >> * Improvement:s use either Done or Implemented Status as you feel right >> * New features: use either Implemented Status >> * Bug: use the Fixed Status >> >> Don't forget to fill the Fix version/s field according to your changes. >> Notably, use Upcoming Branch and not trunk there. >> >> Also, even if when the svn commits comments are correctly done with a >> reference to the Jira issue number we can then get to the commits in >> Fisheye from the Development section of the Jira issue, I'd still recommend >> to put the commits references in a comment. It's always handy, and insures >> we have those references at hand even if the commits comments don't contain >> the Jira issue reference. >> >> Thanks for all the good work :) >> >> Jacques >> > > |
Re: Jira and releases change logs
|
Administrator
|
In reply to this post by Nicolas Malin-2
Thanks Nicolas, I wanted to do it, but did not get a chance, your help is appreciated :)
I take advantage of this mail to correct my sentence below (that's what happen when you "refactor" ;) ) <<For instance for * Improvements: use either Done or Implemented Status as you feel right * New features: use the Implemented Status * Bug: use the Fixed Status >> Jacques Le 18/12/2014 00:20, Nicolas Malin a écrit : > Ok Jacques, > > I propose to complete the page https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities with your sensible > remarks ! > I will do that tomorrow. > > Nicolas > > Le 17/12/2014 15:29, Jacques Le Roux a écrit : >> Hi Committers, >> >> Please take the time to correctly fill the different Jira fields we now use for our releases change logs. >> >> For instance for in >> * Improvement:s use either Done or Implemented Status as you feel right >> * New features: use either Implemented Status >> * Bug: use the Fixed Status >> >> Don't forget to fill the Fix version/s field according to your changes. Notably, use Upcoming Branch and not trunk there. >> >> Also, even if when the svn commits comments are correctly done with a reference to the Jira issue number we can then get to the commits in Fisheye >> from the Development section of the Jira issue, I'd still recommend to put the commits references in a comment. It's always handy, and insures we >> have those references at hand even if the commits comments don't contain the Jira issue reference. >> >> Thanks for all the good work :) >> >> Jacques > > |
Re: Jira and releases change logs
|
Administrator
|
Please Nicolas, when you will do it, add that committers should fill the "Fix Version/s" field with relevant "Unreleased Versions" for improvements
and bug as well Thanks Jacques Le 18/12/2014 08:26, Jacques Le Roux a écrit : > Thanks Nicolas, I wanted to do it, but did not get a chance, your help is appreciated :) > > I take advantage of this mail to correct my sentence below (that's what happen when you "refactor" ;) ) > <<For instance for > * Improvements: use either Done or Implemented Status as you feel right > * New features: use the Implemented Status > * Bug: use the Fixed Status >> > > Jacques > > Le 18/12/2014 00:20, Nicolas Malin a écrit : >> Ok Jacques, >> >> I propose to complete the page https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities with your sensible >> remarks ! >> I will do that tomorrow. >> >> Nicolas >> >> Le 17/12/2014 15:29, Jacques Le Roux a écrit : >>> Hi Committers, >>> >>> Please take the time to correctly fill the different Jira fields we now use for our releases change logs. >>> >>> For instance for in >>> * Improvement:s use either Done or Implemented Status as you feel right >>> * New features: use either Implemented Status >>> * Bug: use the Fixed Status >>> >>> Don't forget to fill the Fix version/s field according to your changes. Notably, use Upcoming Branch and not trunk there. >>> >>> Also, even if when the svn commits comments are correctly done with a reference to the Jira issue number we can then get to the commits in Fisheye >>> from the Development section of the Jira issue, I'd still recommend to put the commits references in a comment. It's always handy, and insures we >>> have those references at hand even if the commits comments don't contain the Jira issue reference. >>> >>> Thanks for all the good work :) >>> >>> Jacques >> >> > |
Re: Jira and releases change logs
|
Administrator
|
To explain why we can reuse Jacopo's explanation
http://markmail.org/message/v3yswhnusu4elta5 And this should go in https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Contributors+Best+Practices http://markmail.org/message/jy3qzmsaoxj56otf Jacques Le 21/12/2014 08:45, Jacques Le Roux a écrit : > Please Nicolas, when you will do it, add that committers should fill the "Fix Version/s" field with relevant "Unreleased Versions" for improvements > and bug as well > > Thanks > > Jacques > > Le 18/12/2014 08:26, Jacques Le Roux a écrit : >> Thanks Nicolas, I wanted to do it, but did not get a chance, your help is appreciated :) >> >> I take advantage of this mail to correct my sentence below (that's what happen when you "refactor" ;) ) >> <<For instance for >> * Improvements: use either Done or Implemented Status as you feel right >> * New features: use the Implemented Status >> * Bug: use the Fixed Status >> >> >> Jacques >> >> Le 18/12/2014 00:20, Nicolas Malin a écrit : >>> Ok Jacques, >>> >>> I propose to complete the page https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities with your sensible >>> remarks ! >>> I will do that tomorrow. >>> >>> Nicolas >>> >>> Le 17/12/2014 15:29, Jacques Le Roux a écrit : >>>> Hi Committers, >>>> >>>> Please take the time to correctly fill the different Jira fields we now use for our releases change logs. >>>> >>>> For instance for in >>>> * Improvement:s use either Done or Implemented Status as you feel right >>>> * New features: use either Implemented Status >>>> * Bug: use the Fixed Status >>>> >>>> Don't forget to fill the Fix version/s field according to your changes. Notably, use Upcoming Branch and not trunk there. >>>> >>>> Also, even if when the svn commits comments are correctly done with a reference to the Jira issue number we can then get to the commits in >>>> Fisheye from the Development section of the Jira issue, I'd still recommend to put the commits references in a comment. It's always handy, and >>>> insures we have those references at hand even if the commits comments don't contain the Jira issue reference. >>>> >>>> Thanks for all the good work :) >>>> >>>> Jacques >>> >>> >> > |
Re: Jira and releases change logs
|
|
In stead of pointing to past mail threads and to where the explanation
'should' go it is better to put the explanation in said place and point to there. Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Sun, Dec 21, 2014 at 11:01 AM, Jacques Le Roux < [hidden email]> wrote: > To explain why we can reuse Jacopo's explanation > http://markmail.org/message/v3yswhnusu4elta5 > > And this should go in https://cwiki.apache.org/ > confluence/display/OFBADMIN/OFBiz+Contributors+Best+Practices > http://markmail.org/message/jy3qzmsaoxj56otf > > Jacques > > Le 21/12/2014 08:45, Jacques Le Roux a écrit : > > Please Nicolas, when you will do it, add that committers should fill the >> "Fix Version/s" field with relevant "Unreleased Versions" for improvements >> and bug as well >> >> Thanks >> >> Jacques >> >> Le 18/12/2014 08:26, Jacques Le Roux a écrit : >> >>> Thanks Nicolas, I wanted to do it, but did not get a chance, your help >>> is appreciated :) >>> >>> I take advantage of this mail to correct my sentence below (that's what >>> happen when you "refactor" ;) ) >>> <<For instance for >>> * Improvements: use either Done or Implemented Status as you feel right >>> * New features: use the Implemented Status >>> * Bug: use the Fixed Status >> >>> >>> Jacques >>> >>> Le 18/12/2014 00:20, Nicolas Malin a écrit : >>> >>>> Ok Jacques, >>>> >>>> I propose to complete the page https://cwiki.apache.org/ >>>> confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities >>>> with your sensible remarks ! >>>> I will do that tomorrow. >>>> >>>> Nicolas >>>> >>>> Le 17/12/2014 15:29, Jacques Le Roux a écrit : >>>> >>>>> Hi Committers, >>>>> >>>>> Please take the time to correctly fill the different Jira fields we >>>>> now use for our releases change logs. >>>>> >>>>> For instance for in >>>>> * Improvement:s use either Done or Implemented Status as you feel right >>>>> * New features: use either Implemented Status >>>>> * Bug: use the Fixed Status >>>>> >>>>> Don't forget to fill the Fix version/s field according to your >>>>> changes. Notably, use Upcoming Branch and not trunk there. >>>>> >>>>> Also, even if when the svn commits comments are correctly done with a >>>>> reference to the Jira issue number we can then get to the commits in >>>>> Fisheye from the Development section of the Jira issue, I'd still recommend >>>>> to put the commits references in a comment. It's always handy, and insures >>>>> we have those references at hand even if the commits comments don't contain >>>>> the Jira issue reference. >>>>> >>>>> Thanks for all the good work :) >>>>> >>>>> Jacques >>>>> >>>> >>>> >>>> >>> >> |
Re: Jira and releases change logs
|
Administrator
|
Nicolas said he will :p
Jacques Le 21/12/2014 11:06, Pierre Smits a écrit : > In stead of pointing to past mail threads and to where the explanation > 'should' go it is better to put the explanation in said place and point to > there. > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Sun, Dec 21, 2014 at 11:01 AM, Jacques Le Roux < > [hidden email]> wrote: > >> To explain why we can reuse Jacopo's explanation >> http://markmail.org/message/v3yswhnusu4elta5 >> >> And this should go in https://cwiki.apache.org/ >> confluence/display/OFBADMIN/OFBiz+Contributors+Best+Practices >> http://markmail.org/message/jy3qzmsaoxj56otf >> >> Jacques >> >> Le 21/12/2014 08:45, Jacques Le Roux a écrit : >> >> Please Nicolas, when you will do it, add that committers should fill the >>> "Fix Version/s" field with relevant "Unreleased Versions" for improvements >>> and bug as well >>> >>> Thanks >>> >>> Jacques >>> >>> Le 18/12/2014 08:26, Jacques Le Roux a écrit : >>> >>>> Thanks Nicolas, I wanted to do it, but did not get a chance, your help >>>> is appreciated :) >>>> >>>> I take advantage of this mail to correct my sentence below (that's what >>>> happen when you "refactor" ;) ) >>>> <<For instance for >>>> * Improvements: use either Done or Implemented Status as you feel right >>>> * New features: use the Implemented Status >>>> * Bug: use the Fixed Status >> >>>> >>>> Jacques >>>> >>>> Le 18/12/2014 00:20, Nicolas Malin a écrit : >>>> >>>>> Ok Jacques, >>>>> >>>>> I propose to complete the page https://cwiki.apache.org/ >>>>> confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities >>>>> with your sensible remarks ! >>>>> I will do that tomorrow. >>>>> >>>>> Nicolas >>>>> >>>>> Le 17/12/2014 15:29, Jacques Le Roux a écrit : >>>>> >>>>>> Hi Committers, >>>>>> >>>>>> Please take the time to correctly fill the different Jira fields we >>>>>> now use for our releases change logs. >>>>>> >>>>>> For instance for in >>>>>> * Improvement:s use either Done or Implemented Status as you feel right >>>>>> * New features: use either Implemented Status >>>>>> * Bug: use the Fixed Status >>>>>> >>>>>> Don't forget to fill the Fix version/s field according to your >>>>>> changes. Notably, use Upcoming Branch and not trunk there. >>>>>> >>>>>> Also, even if when the svn commits comments are correctly done with a >>>>>> reference to the Jira issue number we can then get to the commits in >>>>>> Fisheye from the Development section of the Jira issue, I'd still recommend >>>>>> to put the commits references in a comment. It's always handy, and insures >>>>>> we have those references at hand even if the commits comments don't contain >>>>>> the Jira issue reference. >>>>>> >>>>>> Thanks for all the good work :) >>>>>> >>>>>> Jacques >>>>>> >>>>> >>>>> |
Re: Jira and releases change logs
|
|
Yes I will do it and it's done ! ;)
Don't hesitate to review the change. Sorry for the latency , my community time is like a ballon during a storm Nicolas Le 21/12/2014 12:46, Jacques Le Roux a écrit : > Nicolas said he will :p > > Jacques > > Le 21/12/2014 11:06, Pierre Smits a écrit : >> In stead of pointing to past mail threads and to where the explanation >> 'should' go it is better to put the explanation in said place and >> point to >> there. >> >> Pierre Smits >> >> *ORRTIZ.COM <http://www.orrtiz.com>* >> Services & Solutions for Cloud- >> Based Manufacturing, Professional >> Services and Retail & Trade >> http://www.orrtiz.com >> >> On Sun, Dec 21, 2014 at 11:01 AM, Jacques Le Roux < >> [hidden email]> wrote: >> >>> To explain why we can reuse Jacopo's explanation >>> http://markmail.org/message/v3yswhnusu4elta5 >>> >>> And this should go in https://cwiki.apache.org/ >>> confluence/display/OFBADMIN/OFBiz+Contributors+Best+Practices >>> http://markmail.org/message/jy3qzmsaoxj56otf >>> >>> Jacques >>> >>> Le 21/12/2014 08:45, Jacques Le Roux a écrit : >>> >>> Please Nicolas, when you will do it, add that committers should >>> fill the >>>> "Fix Version/s" field with relevant "Unreleased Versions" for >>>> improvements >>>> and bug as well >>>> >>>> Thanks >>>> >>>> Jacques >>>> >>>> Le 18/12/2014 08:26, Jacques Le Roux a écrit : >>>> >>>>> Thanks Nicolas, I wanted to do it, but did not get a chance, your >>>>> help >>>>> is appreciated :) >>>>> >>>>> I take advantage of this mail to correct my sentence below (that's >>>>> what >>>>> happen when you "refactor" ;) ) >>>>> <<For instance for >>>>> * Improvements: use either Done or Implemented Status as you feel >>>>> right >>>>> * New features: use the Implemented Status >>>>> * Bug: use the Fixed Status >> >>>>> >>>>> Jacques >>>>> >>>>> Le 18/12/2014 00:20, Nicolas Malin a écrit : >>>>> >>>>>> Ok Jacques, >>>>>> >>>>>> I propose to complete the page https://cwiki.apache.org/ >>>>>> confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities >>>>>> >>>>>> with your sensible remarks ! >>>>>> I will do that tomorrow. >>>>>> >>>>>> Nicolas >>>>>> >>>>>> Le 17/12/2014 15:29, Jacques Le Roux a écrit : >>>>>> >>>>>>> Hi Committers, >>>>>>> >>>>>>> Please take the time to correctly fill the different Jira fields we >>>>>>> now use for our releases change logs. >>>>>>> >>>>>>> For instance for in >>>>>>> * Improvement:s use either Done or Implemented Status as you >>>>>>> feel right >>>>>>> * New features: use either Implemented Status >>>>>>> * Bug: use the Fixed Status >>>>>>> >>>>>>> Don't forget to fill the Fix version/s field according to your >>>>>>> changes. Notably, use Upcoming Branch and not trunk there. >>>>>>> >>>>>>> Also, even if when the svn commits comments are correctly done >>>>>>> with a >>>>>>> reference to the Jira issue number we can then get to the >>>>>>> commits in >>>>>>> Fisheye from the Development section of the Jira issue, I'd >>>>>>> still recommend >>>>>>> to put the commits references in a comment. It's always handy, >>>>>>> and insures >>>>>>> we have those references at hand even if the commits comments >>>>>>> don't contain >>>>>>> the Jira issue reference. >>>>>>> >>>>>>> Thanks for all the good work :) >>>>>>> >>>>>>> Jacques >>>>>>> >>>>>> >>>>>> |
Re: Jira and releases change logs
|
Administrator
|
Perfect, thanks Nicolas :)
Jacques Le 23/12/2014 14:27, Nicolas Malin a écrit : > Yes I will do it and it's done ! ;) > > Don't hesitate to review the change. > > Sorry for the latency , my community time is like a ballon during a storm > > Nicolas > Le 21/12/2014 12:46, Jacques Le Roux a écrit : >> Nicolas said he will :p >> >> Jacques >> >> Le 21/12/2014 11:06, Pierre Smits a écrit : >>> In stead of pointing to past mail threads and to where the explanation >>> 'should' go it is better to put the explanation in said place and point to >>> there. >>> >>> Pierre Smits >>> >>> *ORRTIZ.COM <http://www.orrtiz.com>* >>> Services & Solutions for Cloud- >>> Based Manufacturing, Professional >>> Services and Retail & Trade >>> http://www.orrtiz.com >>> >>> On Sun, Dec 21, 2014 at 11:01 AM, Jacques Le Roux < >>> [hidden email]> wrote: >>> >>>> To explain why we can reuse Jacopo's explanation >>>> http://markmail.org/message/v3yswhnusu4elta5 >>>> >>>> And this should go in https://cwiki.apache.org/ >>>> confluence/display/OFBADMIN/OFBiz+Contributors+Best+Practices >>>> http://markmail.org/message/jy3qzmsaoxj56otf >>>> >>>> Jacques >>>> >>>> Le 21/12/2014 08:45, Jacques Le Roux a écrit : >>>> >>>> Please Nicolas, when you will do it, add that committers should fill the >>>>> "Fix Version/s" field with relevant "Unreleased Versions" for improvements >>>>> and bug as well >>>>> >>>>> Thanks >>>>> >>>>> Jacques >>>>> >>>>> Le 18/12/2014 08:26, Jacques Le Roux a écrit : >>>>> >>>>>> Thanks Nicolas, I wanted to do it, but did not get a chance, your help >>>>>> is appreciated :) >>>>>> >>>>>> I take advantage of this mail to correct my sentence below (that's what >>>>>> happen when you "refactor" ;) ) >>>>>> <<For instance for >>>>>> * Improvements: use either Done or Implemented Status as you feel right >>>>>> * New features: use the Implemented Status >>>>>> * Bug: use the Fixed Status >> >>>>>> >>>>>> Jacques >>>>>> >>>>>> Le 18/12/2014 00:20, Nicolas Malin a écrit : >>>>>> >>>>>>> Ok Jacques, >>>>>>> >>>>>>> I propose to complete the page https://cwiki.apache.org/ >>>>>>> confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities >>>>>>> with your sensible remarks ! >>>>>>> I will do that tomorrow. >>>>>>> >>>>>>> Nicolas >>>>>>> >>>>>>> Le 17/12/2014 15:29, Jacques Le Roux a écrit : >>>>>>> >>>>>>>> Hi Committers, >>>>>>>> >>>>>>>> Please take the time to correctly fill the different Jira fields we >>>>>>>> now use for our releases change logs. >>>>>>>> >>>>>>>> For instance for in >>>>>>>> * Improvement:s use either Done or Implemented Status as you feel right >>>>>>>> * New features: use either Implemented Status >>>>>>>> * Bug: use the Fixed Status >>>>>>>> >>>>>>>> Don't forget to fill the Fix version/s field according to your >>>>>>>> changes. Notably, use Upcoming Branch and not trunk there. >>>>>>>> >>>>>>>> Also, even if when the svn commits comments are correctly done with a >>>>>>>> reference to the Jira issue number we can then get to the commits in >>>>>>>> Fisheye from the Development section of the Jira issue, I'd still recommend >>>>>>>> to put the commits references in a comment. It's always handy, and insures >>>>>>>> we have those references at hand even if the commits comments don't contain >>>>>>>> the Jira issue reference. >>>>>>>> >>>>>>>> Thanks for all the good work :) >>>>>>>> >>>>>>>> Jacques >>>>>>>> >>>>>>> >>>>>>> > > |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |