> How long before we end up with 2.2.4 a3 and 2.2.4 b1 with no-one really
> knowing what's going on?
> Taking what is effectively another point onto the version number doesn't
> really help. I can only think of 2.1.7 that was withdrawn, and as long
> as 2.2.4 comes along pretty swiftly, there shou
Brian Lloyd wrote:
>
> I think that is reasonable - in practice I have found that
> many people tend not to upgrade until something is declared
> "final", but your point is taken and a little feedback is
> better than none. I'll make Monday's release 2.2.4 b1.
Please! No! Don't go down the same
On Saturday 18 November 2000 09:07, Joachim Werner wrote:
> > FYI - someone has noticed a problem with the posted
> > 2.2.3 release that needs looking into, so I've unlisted
> > it for the time being. I'll send out a note and re-list
> > it after we dig into this a bit...
>
> Oh no, not this one a
> Oh no, not this one again ...
>
> How good that I learned my lesson from the infamous 2.1.x
> series, when you always replaced or withdrew the latest
> bugfix release due to "some errors" right after we had
> updated all our servers ...
I think "always" is a bit strong...
>
> What about h
> FYI - someone has noticed a problem with the posted
> 2.2.3 release that needs looking into, so I've unlisted
> it for the time being. I'll send out a note and re-list
> it after we dig into this a bit...
Oh no, not this one again ...
How good that I learned my lesson from the infamous 2.1.x
