Mike I honestly prefer just having it as a text file. If you search way back in the logs Doug talked about this long ago, but I generally agree. JIRA would be nice but I just like to keep it up to date in text and in JIRA.
Sorry for the dupe work but it pays off. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 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: Mike Joyce <[email protected]> on behalf of Michael Joyce <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, November 11, 2015 at 11:21 AM To: "[email protected]" <[email protected]> Subject: Updates to CHANGES.txt on commit >Hi folks, > > >It seems like our usual workflow is to update CHANGES on commit (correct >me if I'm wrong here). What do we think about pulling the CHANGES updates >from JIRA as part of our release prep instead? Seems like it would be a >bit less error prone, although I > do understand peoples' desires to have CHANGES up to date all the time. > > >Thoughts? > > >-- Jimmy > > > > > > >
