On Sat, Jul 12, 2014 at 01:16:34PM +0200, Jonas Smedegaard wrote: > Makes perfect sense for a NEWS file to include only major changes (which > in effect means only changes applied to major releases when release > management is strict about not sneaking in major changes in minro > releases). > > So please ignore my too harsh judgement on that file - only thing > confusing is shipping it as "changelog": A changelog is expected to > _cover_ all changes even if not necessarily very granularly - i.e. > shortening to say "Misc. internal code cleanup" is fine, but making a > release with *no* changelog entry is.... weird.
Now that I think about this, it would probably make sense to include the point releases in the RELEASE_NOTES too. Something like: Release 0.4.1 ============= - change - change ... Release 0.4.0 ============= - change - change ... This "changelog" would only include releases in the current 0.X branch (which I think is ok) from the latest .0 release up to the latest point release. This way users can see what was fixed in a later point release (e.g. if they hit a bug in, say, the .0 release, they can check if that's been fixed in .1). FWIW, I did write release notes for the 0.4.1 release [0] but I didn't include them in the RELEASE_NOTES file, so that wouldn't really be much more work. Cheers [0] https://github.com/mpv-player/mpv/releases/tag/v0.4.1
signature.asc
Description: Digital signature
_______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
