On Wed, Jun 19, 2013 at 2:31 PM, Mark Phippard <markp...@gmail.com> wrote:
> On Wed, Jun 19, 2013 at 5:00 AM, Branko Čibej <br...@wandisco.com> wrote: > > Given the number of reports on users@, I think we have to get a 1.8.1 > > with /only/ the 'svnadmin upgrade' crash fix out ASAP. > -1. AFAIK, no data is being compromised and there is not even a functional or performance penalty from being unable to upgrade. I am -0 on this plan. > > This is an embarrassing problem and we have gotten several quick > reports, but it also is not causing any additional problems and it is > only preventing you from doing something you did not need to do in the > first place. > > Rushing around is rarely a good idea and doing a release will only > detract from the resources we need to be investigating and fixing the > early problems coming in. I would prefer to see us do a normal 1.8.1 > release roughly 10-14 days following our launch and include as many of > the early fixes as we can. > I agree. The actually critical bug is the data loss thing (r1494298 group). The initial div 0 problem simply prevents you from upgrading in repos that wouldn't benefit from it anyways. So, let's do a proper 1.8.1 approx. 2 weeks after 1.8.0. -- Stefan^2.
