[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: glib destabilization and ways forward



On Fri, 2006-12-29 at 17:02 -0200, Otavio Salvador wrote:
> Thomas Bushnell BSG <tb@becket.net> writes:
> 
> > 2) Decide that glib can migrate into testing, with the particular change
> > of checking key values reverted to its pre-2.12.5 behavior, since this
> > is a destabilizing change in the Debian context.
> 
> This looks to be the best option since it preserves the backward
> compatibility while also brings the bugfixes of the new release on
> Etch. I think we should keep on mind that other applications can also
> sufer from same problem as GNUCash does and there's no time to us to
> detect them.

Incidentally, while this is outside my specific purview as gnucash
maintainer, I think that the *individual* changes made to glib should be
*individually* checked, to see whether they *individually* fix RC bugs,
and that documentation should be presented before any request to
transition glib into testing is made.

Thomas

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: