Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C06299FD9 for ; Fri, 3 Feb 2012 10:42:09 +0000 (UTC) Received: (qmail 75629 invoked by uid 500); 3 Feb 2012 10:42:08 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 74955 invoked by uid 500); 3 Feb 2012 10:41:59 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 74931 invoked by uid 99); 3 Feb 2012 10:41:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2012 10:41:52 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 94.246.96.44 is neither permitted nor denied by domain of jens.rantil@telavox.se) Received: from [94.246.96.44] (HELO smtp1-4.ilait.se) (94.246.96.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2012 10:41:42 +0000 Received: from ex-hub2.hosting.local (unknown [82.99.18.110]) by smtp1-4.ilait.se (Postfix) with ESMTPS id B671A70107 for ; Fri, 3 Feb 2012 10:41:21 +0000 (UTC) Received: from ex-mbx4.hosting.local ([10.46.16.34]) by ex-hub2.hosting.local ([82.99.18.110]) with mapi; Fri, 3 Feb 2012 11:41:21 +0100 From: Jens Rantil To: "dev@couchdb.apache.org" Date: Fri, 3 Feb 2012 11:42:12 +0100 Subject: SV: backport of couchdb Thread-Topic: backport of couchdb Thread-Index: AczgWNN/NZDBb5UnQBGETpsS2yJ1LAAbSf7Q Message-ID: <850092711C09C042B93EC2F4F2E8B1E7027741223B@ex-mbx4.hosting.local> References: <850092711C09C042B93EC2F4F2E8B1E70277411C42@ex-mbx4.hosting.local> <1328041459.6368.26.camel@julia.gcs.org.hu> In-Reply-To: Accept-Language: en-US, sv-SE Content-Language: sv-SE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, sv-SE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hi again everyone, I am happy to get a discussion going about this. I'd say Debian is a major = platform for servers. Therefor, I believe CouchDB should exist there - with= a reasonable modern version. Sure, you can install from source. However, w= ith CouchDB and it's replication features it should be easy to roll it out = to a multitude of Debian servers and kick off replication. Also, previously Couchbase was hosting a (sadly, buggy) Debian package. Aft= er the death of the Couchbase package[1] there is no modern Debian package = alternative anymore. To keep this discussion going - what did you think of Jan's proposal to set= up a Debian maintainer mailing list? As of the initial question, shall Deb= ian stable installations be living with 0.11 for another ~6 months? I guess= so. /J -----Ursprungligt meddelande----- Fr=E5n: Jan Lehnardt [mailto:jan@apache.org]=20 Skickat: den 31 januari 2012 21:42 Till: dev@couchdb.apache.org Kopia: Laszlo Boszormenyi =C4mne: Re: backport of couchdb Hi Laszlo, On Jan 31, 2012, at 21:24 , Laszlo Boszormenyi wrote: > Hi, >=20 > First, I'm an official DD and the maintainer of CouchDB. Pleased to meet you and thanks for weighing in on this discussion :) >> As for the back porting, Debian doesn't directly manage any packages. >> Everything has a package maintainer who may or may not be part of the=20 >> Debian staff, so it really does land on the maintainer. And I don't=20 >> see how you could back port fixes from, say, 1.x.x to 0.x.x. > Let me ask an other way. Is CouchDB expected to change a lot=20 > internally? I think it is. The question, I think, is how much end-users will be affecte= d by these changes (upgrade trouble, incompatibilities etc.) We are doing o= ur best to not break BC (according to semver.org) and make upgrades seamles= s and well documented. > What about helping downstream with security fixes? We could start a new mailing list package-maintainers@couchdb.apache.org where downstream folks can subscribe and get notified about impeding releas= es as well as security notices. Would that be a good first step? What else could we do to help you downstream? > When CouchDB 1.2.0 is expected to be released? We are expecting to call a vote in the next few days (pending release manag= er time). As per our process, it'll take 4-5 days after the initial call fo= r voting to get the release out (if the votes don't go through and if issue= s are found, this process is reset). Let us know if you have any other questions and thanks again for helping ou= t! Cheers Jan --=20