On 21.09.2009, at 06:08, Benoit Chesneau <[email protected]> wrote:
On Sun, Sep 20, 2009 at 11:48 PM, Chris Anderson
That's the sort of thing that'd get backported for 0.10.1 anyway,
so I
don't think it's a blocker. Also, probably a fairly easy patch.
Chris
Well it's really annoying to have such error in logs when you are in
production. I've also updated the bug : when you delete a db witch is
continuously replicatedit create an error too on the machine handling
replication when I delete a database on source. There maybe other side
effect.
More over, due to apache process, 10.1 could appear very long time
after 10.0 and imo having this known obvious errors fixed before the
release may be better.
I think I see where this is coming from, but rather see it perceived
that bugfix updates to a stable branch should happen in a timely
manner. We can't hold back releases forever and we should demonstrate
that we can release 0.10.1 quickly, if needed.
I hope this addresses your concern.
Cheers
Jan
--
