Re: Fwd: Debian 13 (trixie) freeze schedule released

--EdoMail67961260_154ef1c_13ac
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline




>

>  I was indeed intending a 1.31.0 release if base.

>  I think it would probably be possible to avoid the library version chan=
ge and do a 1.30.1 release instead, though that would need careful checkin=
g and possibly a degree of rewriting any changes that break abi.

>  However, am I right in thinking that would be pointless if GUI and back=
 need a library version change at the next release anyway?




--EdoMail67961260_154ef1c_13ac
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div id=3D=22edo-original=22><div><blockquote type=3D=22cite=22 style=3D=22=
margin: 1ex 0 0 0 =21important; border-left: 1px =23ccc solid =21importan=
t; padding-left: 0.4ex =21important;=22></blockquote><blockquote type=3D=22=
cite=22 style=3D=22margin: 1ex 0 0 0 =21important; border-left: 1px =23cc=
c solid =21important; padding-left: 0.4ex =21important;=22>I was indeed i=
ntending a 1.31.0 release if base.</blockquote><blockquote type=3D=22cite=
=22 style=3D=22margin: 1ex 0 0 0 =21important; border-left: 1px =23ccc so=
lid =21important; padding-left: 0.4ex =21important;=22>I think it would p=
robably be possible to avoid the library version change and do a 1.30.1 r=
elease instead, though that would need careful checking and possibly a de=
gree of rewriting any changes that break abi.</blockquote><blockquote typ=
e=3D=22cite=22 style=3D=22margin: 1ex 0 0 0 =21important; border-left: 1p=
x =23ccc solid =21important; padding-left: 0.4ex =21important;=22>However=
, am I right in thinking that would be pointless if GUI and back need a l=
ibrary version change at the next release anyway=3F</blockquote></div></d=
iv>
--EdoMail67961260_154ef1c_13ac--