summaryrefslogtreecommitdiffstats
path: root/Help/release/index.rst
Commit message (Collapse)AuthorAgeFilesLines
* Begin post-3.2 developmentBrad King2015-02-051-0/+2
|
* Help: Drop development topic notes to prepare releaseBrad King2015-02-051-2/+0
| | | | | Release versions do not have the development topic section of the CMake Release Notes index page.
* Help: Rename 3.x.0 release notes to 3.xBrad King2015-02-051-3/+3
| | | | | | | | | | | | | | In commit v3.0.0-rc1~9 (Help: Rename 3.0 release notes to 3.0.0, 2014-02-19) we anticipated the possibility of bugfix-only release notes. However, in practice we have no release notes for bug fix releases because we do not cover bug fixes in release notes at all, only new features. Instead we've been updating the feature-level release notes document in bug fix releases, treating errors in the document as bugs. It makes more sense to maintain release notes at the feature-release level, so rename the documents accordingly. Also update the document titles and intro text to refer only to feature versions and not bugfix versions.
* Help: Consolidate 3.2 release notesBrad King2015-02-051-0/+1
| | | | | | | | | | | | | | Move all development release notes into a new version-specific document: tail -q -n +3 Help/release/dev/* > Help/release/3.2.0.rst git rm -- Help/release/dev/* except the sample topic: git checkout HEAD -- Help/release/dev/0-sample-topic.rst Reference the new document from the release notes index document. Add a title and intro sentence to the new document by hand.
* Begin post-3.1 developmentBrad King2014-10-141-0/+2
|
* Help: Drop development topic notes to prepare releaseBrad King2014-10-141-2/+0
| | | | | Release versions do not have the development topic section of the CMake Release Notes index page.
* Help: Consolidate 3.1 release notesBrad King2014-10-101-0/+1
| | | | | | | | | | | | | | Move all development release notes into a new version-specific document: tail -q -n +3 Help/release/dev/* > Help/release/3.1.0.rst git rm -- Help/release/dev/* except the sample topic: git checkout HEAD -- Help/release/dev/0-sample-topic.rst Reference the new document from the release notes index document. Add a title and intro sentence to the new document by hand.
* Begin post-3.0 developmentBrad King2014-02-191-0/+2
|
* Help: Drop development topic notes to prepare releaseBrad King2014-02-191-2/+0
| | | | | Release versions do not have the development topic section of the CMake Release Notes index page.
* Help: Rename 3.0 release notes to 3.0.0Brad King2014-02-191-1/+1
| | | | | Bug-fix releases 3.0.x may have their own notes so this will look more consistent.
* Help: Add CMake 3.0 Release NotesBrad King2014-02-111-0/+2
| | | | | | | Manually read through version control history since the 2.8.12.2 release and write release notes for important user-facing changes. Co-Author: Stephen Kelly <steveire@gmail.com>
* Help: Add documents to collect notes between releasesBrad King2014-02-041-0/+6
| | | | | | | | | | | Add a release/dev.txt file and include it from release/index.rst in development versions. Add a "Changes Since Release" section with a toctree that globs adjacent "dev/*" documents. Add a sample topic document explaining how topic-specific release note documents work. This approach will allow developers to write release notes for their changes as they are made. The release manager may then consolidate and organize the notes for a specific release version.
* Help: Add documents for release notesBrad King2014-02-041-0/+8
Add a release/index.rst document titled "CMake Release Notes" to hold the toctree for release notes. Add a "Release Notes" section to the top-level html document index to link to the new document.
generated by cgit v0.12 at 2024-09-15 06:00:48 (GMT)