Jack, can you answer the question of our release manager, please? We are very close to the next stable release and thus our release managers are very picky what change they allow to go in.
I know that minor botan releases are meant to be API/ABI compatible, and those changes don't seem to mangle the API, but we want to strictly follow our release process, so we don't accidentaly introduce some breakage at this point of time. If those issues are not severe enough it might be better idea to get them in using other mechanisms (stable-proposed-updates) in next point minor Debian release. Thank you very much, Ondrej ---------- Forwarded message ---------- From: Jonathan Wiltshire <j...@debian.org> Date: Fri, Mar 15, 2013 at 9:43 PM Subject: Re: Bug#701817: unblock: botan1.10/1.10.4-1 To: OndÅ?ej Surý <ond...@debian.org>, 701...@bugs.debian.org Control: tag -1 moreinfo Hi Ondřej, On Wed, Feb 27, 2013 at 02:52:52PM +0100, Ondřej Surý wrote: > Please unblock package botan1.10 > > Hi, > > I would like to pre-mediate the inclusion of 1.10.4 (e.g. new upstream version). > > The patch is very small and fixes three issues. Upstream changelog: What is the impact and severity of these issues? I don't have enough knowledge of the package to assess this from the upstream release notes, and the BTS is lacking any clues. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 <directhex> i have six years of solaris sysadmin experience, from 8->10. i am well qualified to say it is made from bonghits layered on top of bonghits -- Ondřej Surý <ond...@sury.org>
signature.asc
Description: PGP signature