On Sun, Jul 18, 2010 at 20:09:33 (CEST), Jean-Baptiste Kempf wrote: > On Sun, Jul 18, 2010 at 08:02:50PM +0200, Reinhard Tartler wrote : >> It's not, and I've elaborated why in the paragraph you've killed in >> your reply. > What do you need? sha1s of the commits?
That sounds great. Even better if in form of links to gitweb, so that one can directly inspect the diff. >> This has not changed, but AFAIUI, there are only very focused and >> documented changes in bugfix branches. Maybe I'm wrong here? If yes, >> then a stable release update needs to cherry-pick the relevant changes. >> Nothing really surprising, IMHO. > This has never been the case. See below, > >> I think the misunderstanding is about the 1.0-bugfix and 1.1-bugfix >> branches. Can you perhaps explain me the update/commit policy in the >> 1.0-bufix branch? what patches qualify and what don't? Is there a wiki >> page or something I can read about? > > There is no defined policy. > > ABI and API should be compatible. > > But, various fixes, or small improvements should go there. > But also new features can enter there, as 1.1.1 can show... > > Those branches aren't 'small fixes' and 'security' only. Hm, so they probably don't meet the stable release update policy of neither debian nor ubuntu. That makes things of course more difficult. So what basically would indeed help was if you as upstream could help us identify to security or otherwise important changes (patches). Ideally in form of a VSA or at least in a ChangeLog file or something. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 _______________________________________________ pkg-multimedia-maintainers mailing list firstname.lastname@example.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers