This would make a fantastic page in the wiki :-) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----Original Message----- From: Lewis John Mcgibbney <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Thursday, January 28, 2016 at 12:17 PM To: Omkar Reddy <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Issue Tracking >Hi Omkar, >Good job on committing CLIMATE-379. >Here are some pointers to make your life a bit easier. > > 1. When you open a pull request in Github please name the issue after > the issue created in Jira. E.g. CLIMATE-379 - Allows dataset > customisation (you did this fine) > 2. When you make a commit to master, please have the commit message > shadow the Jira issue title but append "this closes #${Github Issue > Number}" e.g. CLIMATE-379 - Allows dataset customisation this closes >#276 > 3. What 2 above does, is automatically closes the referenced issue on > Github. All of this is shadowed over to the relevant Jira issue as >well. > 4. Then all you need to do is go over to the Jira issue and resolve it >:) > >Thanks it. The workflow is pretty simple and all it comes down to is a >descriptive commit message as well as ensuring a Jira issue is created for >every source code alteration you wish to make. > >Thanks, good to have you able to commit to source. > >Lewis > >P.S. I went ahead and resolved >https://issues.apache.org/jira/browse/CLIMATE-379 for you this time :) > >-- >*Lewis*
