[FFmpeg-devel] Roundup being migrated

Michael Niedermayer michaelni
Fri Feb 13 23:50:04 CET 2009

On Fri, Feb 13, 2009 at 11:11:34PM +0100, Luca Barbato wrote:
> Michael Niedermayer wrote:
> > On Fri, Feb 13, 2009 at 08:44:14PM +0100, Luca Barbato wrote:
> >> Michael Niedermayer wrote:
> >>> On Fri, Feb 13, 2009 at 07:27:22PM +0100, Diego Biurrun wrote:
> >>>> On Fri, Feb 13, 2009 at 07:22:17PM +0100, Luca Barbato wrote:
> >>>>> Roundup home changed, now it is hosted by axant.it, the db used is some 
> >>>>> days old I should be able to get back the newer one shortly so tell me 
> >>>>> if you can accept to have lost some data but you want it running now or 
> >>>>> could wait till Monday to get the latest db from the previous box.
> >>>> I prefer not to lose data, but I must admit it's very inconvenient that
> >>>> roundup will not be (fully) available for the bug fixing weekend.
> >>> The word incompetent comes to mind
> >>> first because one doesnt do such a move when the tracker is needed most and
> >>> second because one doesnt fail and require 3 days to copy some db.
> >> The word "getting notified after they cut the cables" comes to mind.
> > 
> > i didnt say you are incompetent, rather someone clearly is.
> Well IF I had moved everything when I started setting it up on the other 
> site and IF I hadn't wait to the last to make the switch probably you 
> wouldn't notice the issue at all... Well I got sidetracked by real life 
> commitments this week =|
> > how much data would be lost? if its just a few entries someone could copy
> > and paste them from the ML / resend
> The current update state of roundup is the following:
> - the website part of roundup has been setup by Feb 3 (including db 
> dump), here is my fault not automatically syncing it from that time...
> - the mail integration hadn't been done yet but I could get it working 
> tomorrow for sure.
> - roundup is currently live and usable from web

so people can add new bug reports?
if so what will happen when you again get access to the old db? can it be
merged in at all?
It is VERY important that issue numbers do not change from what they where
before, besides the confusion, any reply to an old issue via mail/ML will
let hell loose if the issue numbers changed ..

IMO the most important thing now is to avoid further damage. And i do not
think roundup can easyily be put back online before all past data has
been included be that via getting access to the db or via manually reentering

Let me reiterate, if you take a 10 day old db and let people work with that
it will be impossible to merge the old issues because their issue numbers will
be already used by others, the ML, mphq/incoming, ... will turn to chaos

Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

> ... defining _GNU_SOURCE...
For the love of all that is holy, and some that is not, don't do that.
-- Luca & Mans
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20090213/71c9f27a/attachment.pgp>

More information about the ffmpeg-devel mailing list