diff options
author | Alexander Berntsen <bernalex@gentoo.org> | 2014-08-12 23:10:33 +0200 |
---|---|---|
committer | Alexander Berntsen <bernalex@gentoo.org> | 2014-08-12 23:54:31 +0200 |
commit | c315fd9e623f33dff2ba00ed758638cada04c547 (patch) | |
tree | fa5da9ebd4e8284805bc81f83d0e7085af0dafc3 /DEVELOPING | |
parent | Note the use of X-by in DEVELOPING (diff) | |
download | portage-c315fd9e623f33dff2ba00ed758638cada04c547.tar.gz portage-c315fd9e623f33dff2ba00ed758638cada04c547.tar.bz2 portage-c315fd9e623f33dff2ba00ed758638cada04c547.zip |
DEVELOPING: Update RELEASE-NOTES & NEWS in commit
Signed-off-by: Alexander Berntsen <bernalex@gentoo.org>
Reviewed-by: Brian Dolbec <dolsen@gentoo.org>
Diffstat (limited to 'DEVELOPING')
-rw-r--r-- | DEVELOPING | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/DEVELOPING b/DEVELOPING index b1b3390f6..98c34b2a3 100644 --- a/DEVELOPING +++ b/DEVELOPING @@ -174,6 +174,11 @@ change a lot of unrelated things. This makes it easier to see what parts of the system have actually changed. It also makes it easier to cherry-pick and revert commits. Use your common sense! +When you make a significant change, make sure to update RELEASE-NOTES +for the to-be-released version. Very significant changes should be +mentioned in NEWS as well. See the current entries to these files for +examples of what constitutes significant. + Commit messages --------------- |