> Jeff Hill wrote:
> >
> >Can we automate moving the information that is mantis (bug name, bug id,
> >subsystem name) into the release notes?
>
> I question the usefulness of doing this in practice. For someone
> interested in the status of a specific bug it would be quicker to type
> the id# into the Bug ID box present on almost every Mantis page.
Yes, but the bug title, bug id, and subsystem name are all that I am
advocating be placed in the release notes. Should there be a person with
gluttony for the gory details they can always dig deeper within Mantis.
This was my thought process:
=> Patch releases are to contain only bug fixes
=> Bug fixes should be described in detail within Mantis
=> The mantis one line bug title and bug number might therefore be quite
sufficient as a release note
=> The gathering of this information might easily be automated
> but I wouldn't want us to get into the position where a developer
> doesn't bother to write an explicit entry in the notes for a particular
> change because "the Mantis bug report explains everything".
Or one could advocate that Mantis should prescribe the release notes, and
not visa-versa, thereby arriving at the conclusion that if the situation
isn't described in Mantis then it should be. If not, then there will be no
entry in the release notes.
Jeff
> -----Original Message-----
> From: Andrew Johnson [mailto:[email protected]]
> Sent: Monday, November 28, 2005 3:28 PM
> To: 'EPICS core-talk'
> Subject: Re: Mantis bugs
>
> Jeff Hill wrote:
> >
> >Can we automate moving the information that is mantis (bug name, bug id,
> >subsystem name) into the release notes?
>
> I question the usefulness of doing this in practice. For someone
> interested in the status of a specific bug it would be quicker to type
> the id# into the Bug ID box present on almost every Mantis page. If
> there are any other implications due to a change, the developer should
> have written suitable words in the release notes anyway - there's
> nothing stopping the person who fixes a bug from including the bug ID in
> any entry they make in the release notes.
>
> I don't think there would be much difficulty in including a summary of
> bugs closed in the release notes if the concensus is that they should be
> there, but I wouldn't want us to get into the position where a developer
> doesn't bother to write an explicit entry in the notes for a particular
> change because "the Mantis bug report explains everything".
>
> - Andrew
> --
> * * Matt Santos / / Leo McGarry * * For a Brighter America * *
- References:
- Re: Mantis bugs Andrew Johnson
- Navigate by Date:
- Prev:
Re: Mantis bugs Andrew Johnson
- Next:
Re: R3.14.8 makeBaseApp.pl - File::Find problem on cygwin Ralph Lange
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Mantis bugs Andrew Johnson
- Next:
RE: R3.14.8 makeBaseApp.pl Jeff Hill
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|