On Sat, Jul 12, 2014 at 12:24:11AM +0200, Jonas Smedegaard wrote: > reopen 722997 > thanks > > Thanks for including upstream release notes. That file, however, seems > at most a NEWS file: It is apparently an unmaintained broad overview of > changes for some specific release - without mention of which one, but > didn't at all since it was included and mentions only two git hashes, no > version numbers.
The RELEASE_NOTES file *is* maintained (in fact *I* maintain it, since I somehow became mpv's release manager) and it refers to the latest major release (0.X.0). It's also not really "broad", since it reflects pretty accurately what user-facing changes went into the release (of course, I could have missed something since the 0.4.0 release had something like 1400 new commits). But I can see why it's confusing. I guess I can add the version number at the top or something, that's not a problem. The notes however do not include changes in the point releases (e.g. 0.4.1), which are only fixes for regressions introduced by previous releases in the same 0.X branch. Not sure if it would make sense to include them as well (or how). In the future there won't be as many point releases as in the past tough (which is a good thing I guess), since major releases will be released more often, so maybe this isn't that much of a problem. I've also thought about having a proper ChangeLog file that includes all the releases, but it would be difficiult to maintain due to mpv's release process (releases come from separate release/0.X branches, which are never merged back into master, so at best the chanelog would only include releases from the same 0.X series). I'm still getting the hang of this release manager business tough (v0.4.0 was my first release, snd it was a pretty big one), so suggestions are appreciated. Cheers
signature.asc
Description: Digital signature
