Release Checklist: Difference between revisions

530 bytes removed ,  10 December 2019
Start overhauling the template.
(Compare this template page with 5.0.0 Release Checklist.)
(Start overhauling the template.)
Line 1: Line 1:
== 6.1 Release Tasks ==
Please use
 
<strike></strike>
 
to mark items as done.
 
== Kickoff ==
 
=== Update gnulib to latest version ===
:Completion Date:
:Must occur first as it could resolve existing, or create new, bug reports. You should run <code>./bootstrap</code> in the source tree after updating to the new gnulib version.
 
=== File bug reports ===
:Completion Date:
* Put out a general call for reports on maintainers@octave.org and help@octave.org mailing-list for all outstanding unreported known bugs.
 
=== Review submitted patches on Savannah ===
:Completion Date:
* Submitted patches from '''bug tracker''' included.
* Submitted patches from '''patch tracker''' included.
 
=== Review open bugs on Savannah ===
:Completion Date:
* Review bugs and update to correct category, such as "Patch submitted", correct title if necessary.
* Add "must-fix" items to [[6.1 Release Bug Fix List]].
 
=== GPL License activities ===
:Completion Date:
* Update copyright statements for all source controlled files.
* Update dates in any other locations (launch message, citation, MXE files, etc.).
* Add any new contributors to {{Path|contributors.in}} who wish to be mentioned (don't add them without permission).
 
=== Style-check code base ===
:Completion Date:
: This will produce lots of whitespace changes, but no behavior changes. '''Must occur after patches have been added''', since whitespace changes can prevent patches from applying
* m-file style check
* C++ style check
 
 
== Repeat until all bugs are resolved ==
 
=== Run lint checker on code base ===
:Completion Date:
* Compiling with <code>-fsanitize=undefined</code> and running <code>make check</code>, <code>cppcheck</code>, etc.
** PVS static analyzer results [[PVS static analyzer - 5.0 Release]]


<!----------------------------------------------------------------------------->
# Update gnulib to latest version
#: Must occur first as it could resolve existing, or create new, bug reports
#: Done.  You should run bootstrap in the source tree after updating to the new gnulib version.
#: Completion Date:
<!----------------------------------------------------------------------------->
# File bug reports for all outstanding bugs known, but not reported
#* Put out a general call for reports on Octave-Maintainers and Octave-Help list
#: Completion Date:
<!----------------------------------------------------------------------------->
# Review patch tracker/bug list for any patches submitted that may be included before release
#: Completion Date:
<!----------------------------------------------------------------------------->
# Identify Bugs which '''must''' be fixed prior to release
#* Review bugs on tracker for possible inclusion in list
#* Review bugs and update to correct category, such as Patch submitted
#: Completion Date:
<!----------------------------------------------------------------------------->
# Clear all bugs identified as must-fix
#* See [[6.1 Release Bug Fix List]]
#: Completion Date:
<!----------------------------------------------------------------------------->
# GPL License activities
#* Update Copyright statements for all source controlled files
#* Update dates in any other locations (launch message, citation, MXE files, etc.)
#* Add any new contributors to contributors.in
#: Completion Date:
<!----------------------------------------------------------------------------->
# Style-check code base
#* This will produce lots of whitespace changes, but no behavior changes
#* Must occur after patches have been added since whitespace changes can prevent patches from applying
#* m-file style check. Completion Date:
#* C++ style check. Completion Date:
<!----------------------------------------------------------------------------->
# Run lint checker on code base
#* Possibilities include compiling with -fsanitize=undefined and running 'make check', cppcheck, etc.
#* PVS static analyzer results [[PVS static analyzer - 5.0 Release]]
#* Compile with -fsanitize=undefined and run 'make check'
#: Completion Date:
<!----------------------------------------------------------------------------->
<!----------------------------------------------------------------------------->
# Verify 'make check' is passing on all buildbot combinations of OS and compilers
# Verify 'make check' is passing on all buildbot combinations of OS and compilers