incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Newson <robert.new...@gmail.com>
Subject Re: Production use of Release 1.1
Date Tue, 24 May 2011 08:19:51 GMT
1.1 is already feature frozen, we are diligently working to resolve
the remaining blocking bugs and drive towards a release. I am
optimistically planning for another release candidate by the end of
the week.

B.

On 24 May 2011 08:58, Harald Dietrich <harald.dietrich@iqundu.com> wrote:
> Thanks for the quick reply!
>
> I guess I have to check out the list of open issues more often. After having
> monitored the list for a while I did not see any changes. Last open issue was
> the packaging. And depending on the messages in this list I assumed that is
> all that is planned for release 1.1
>
> Are there any plans for a feature freeze for release 1.1 so one can give an
> estimation of when 1.1. will be ready for production use?
>
> Thanks,
> Harald
>
> Am Montag 23 Mai 2011, um 10:38:05 schrieb Gabor Ratky:
>> Harald,
>>
>> there are currently 5 outstanding issues discovered affecting CouchDB 1.1,
>> 4 of them being blockers [1]. You should _carefully_ look at those issues
>> and see if it can, in any way affect you. For instance, there are two
>> blocker issues related to replication so if you are planning on
>> replicating inside or to/from your production environment, it could affect
>> you. There will be no 1.1 release until these issues are fixed and there
>> might be other issues still to be found as part of the 1.1 release
>> process.
>>
>> Answering your original question, while we benefit from 1.1 improvements as
>> well (and have been testing it locally), we will keep running 1.0.2 in
>> both our staging and production environments, until the release process is
>> complete and 1.1 is officially released.
>>
>> Gabor
>>
>> [1] https://issues.apache.org/jira/browse/COUCHDB/fixforversion/12314933
>> On Monday, May 23, 2011 at 10:24 AM, Harald Dietrich wrote:
>> Hi,
>>
>> > we are waiting for the official release 1.1 already for a while. It
>> > includes some improvements, which are quite important for us.
>> >
>> > As there seem to be no reliable release date, but several people seem to
>> > make use of CouchDB 1.1 for a while, I would like to know who is making
>> > use of the 1.1 release already and what is your experience in regards to
>> > production readiness.
>> >
>> > Thanks for your feedback!
>> >
>> > Best regards,
>> >
>> > Harald Dietrich
>> > (iqundu GmbH)
>
>
> --
> _________________________________
>
> iqundu GmbH
> Kronstadter Straße 8
> 81677 München
>
> Phone: +49 (0)   89 / 800 440 22
> Mobile: +49 (0) 176 / 450 405 09
> Fax:   +49 (0) 3212 / 13 25 292
>
> harald.dietrich@iqundu.com
> http://www.iqundu.com
>
> iqundu GmbH, Sitz: München
> Amtsgericht München HRB 186525
>
> Geschäftsführer: Michael Rau, Andreas Kretschmer
>
> Die in dieser E-Mail enthaltenen Informationen sind vertraulich und können
> rechtlich bedeutsam sein. Sie sind ausschließlich für den Adressaten bestimmt
> und jeglicher Zugriff durch andere Personen ist unzulässig. Falls Sie nicht
> der beabsichtigte Empfänger sind, ist jegliche Veröffentlichung, Verteilung
> oder sonstige in diesem Zusammenhang stehende Handlung untersagt und unter
> Umständen rechtswidrig. Herkömmliche E-Mails sind zudem nicht gegen Zugriff
> geschützt und können mit und ohne Einfluss von Dritten verloren gehen,
> verändert oder verfälscht werden. Eine Haftung für die Unversehrtheit von E-
> Mails oder hieraus entstandene Schäden kann daher nicht übernommen werden.
>
> The information in this e-mail is confidential and may be legally privileged.
> It is intended solely for the addressee and access to the e-mail by anyone
> else is prohibited. If you are not the intended recipient, any disclosure,
> distribution or any action taken or omitted to be taken in reliance on it, is
> prohibited and may be unlawful. Common e-mails are not protected against
> access by third persons and therefore might be lost, changed or falsified,
> with or without any interference by third persons. We cannot accept any
> responsibility for the integrity of e-mails or for any damages resulting out
> of these circumstances.
>

Mime
View raw message