Bug#658829: transition: db-defaults
I have just found that there is a transition tracker for db5.3 transition.
Did the release team came to conclusion whether to do this transition or not?
On Mon, Feb 6, 2012 at 20:17, Ondřej Surý <email@example.com> wrote:
> 2012/2/6 Julien Cristau <firstname.lastname@example.org>:
>> On Mon, Feb 6, 2012 at 09:55:47 +0100, Ondřej Surý wrote:
>>> db4.7 has been reduced just to utils and db4.8 still has some
>>> dependencies left (with most prominent python2.7), but I would
>>> like to try python2.7 with db5.3, maybe it will help the build
>>> failures Martin Pitt is seeing.
>> Sounds like that should be tested first, otherwise there's little point.
> The main point is to keep close to upstream releases. But I guess
> you are right that it deserves to be tested prior to uploading. Where
> I can buy some free time? :)
> Ondřej Surý <email@example.com>
Ondřej Surý <firstname.lastname@example.org>