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 3A4D2E27D for ; Thu, 21 Feb 2013 18:13:55 +0000 (UTC) Received: (qmail 40402 invoked by uid 500); 21 Feb 2013 18:13:54 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 40356 invoked by uid 500); 21 Feb 2013 18:13:54 -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 40341 invoked by uid 99); 21 Feb 2013 18:13:54 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Feb 2013 18:13:54 +0000 Received: from localhost (HELO mail-ie0-f177.google.com) (127.0.0.1) (smtp-auth username nslater, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Feb 2013 18:13:54 +0000 Received: by mail-ie0-f177.google.com with SMTP id 16so11751292iea.36 for ; Thu, 21 Feb 2013 10:13:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:content-type:x-gm-message-state; bh=i9N+v2v3aPJcvBTVSFK5q0NVSgEyh07hQh7//EO+NUc=; b=D3o3ZbJHlOge103KhfKVf+sHnwezo95lilHGD4O0gwYkMfXuSjDbGvJ049id64NsrF Yg9iFHnYf4ocaaP9PC5muDUJZLneML8XODgv3xm4G1OUcsnSJ8H1JhSRTDcHG/kir4qk D1iSHGHHTwvkMDrw+JS+g9pLTQmR49UYVAZ/p2vI0WVQfzPt/TbWNiKYki4Rdmnuk3+h Oa9GZRJPqh/FGxcDG/8n9RtNGIDaPJdMhHGUvpMiPh3WlA9BRPzK0PlcTKJjqdqn+DSP QJYEn8Ejg6Q0M72WJHxmhE3yZMzPJGky8q3gc4JXvgAdurF7xBi4dTf+VI26lmJ0bALO GcyA== MIME-Version: 1.0 X-Received: by 10.50.153.198 with SMTP id vi6mr13721846igb.112.1361470433475; Thu, 21 Feb 2013 10:13:53 -0800 (PST) Received: by 10.50.138.198 with HTTP; Thu, 21 Feb 2013 10:13:53 -0800 (PST) X-Originating-IP: [178.250.115.206] In-Reply-To: References: <70FBD9BE-D6C7-4269-80D0-C3509DED6301@apache.org> Date: Thu, 21 Feb 2013 18:13:53 +0000 Message-ID: Subject: Re: Releases procedure From: Noah Slater To: "dev@couchdb.apache.org" Content-Type: multipart/alternative; boundary=e89a8f22c6818f3cc304d6400911 X-Gm-Message-State: ALoCoQnDtfwJ4EOS4Utj5DWwEkk8PpW3zbTPrrMQ5mGuY4W8SAX4wpSrjcQrltE6ba6yif4mzZPR --e89a8f22c6818f3cc304d6400911 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I will do when my scripts are producing them. I think Bob is looking at trying to replicate. On 21 February 2013 18:12, Jan Lehnardt wrote: > Hey Noah, sorry for being snipey. > > On Feb 21, 2013, at 19:07 , Noah Slater wrote: > > > I know. I've been busy working on my automation. > > > > Steps to reproduce: > > > > Spin up an xlarge Ubuntu AMI. Use most recent supported Ubuntu in quick > > launch wizard. (ami-640a0610) > > > > Try "make distsign" > > > > That's it. > > Would be awesome if someone could send failure logs here. > > Cheers > Jan > -- > > > > > > > > On 21 February 2013 17:59, Jan Lehnardt wrote: > > > >> > >> On Feb 21, 2013, at 18:41 , Noah Slater wrote: > >> > >>> The hours and days I am spending on this release are trying to make u= p > >> for > >>> a non-deterministic test suite that can take hours and hours to > babysit, > >> to > >>> the point where I am having to automate my way around it. > >> > >> I still haven=92t seen any logs that I could use to help debug this. > >> > >>> > >>> The NEWS and CHANGES stuff should take 5-10 minutes tops. But if it i= s > >>> neglected, then the problem compounds, because now I have to look > through > >>> the timelines and organise things so we are consistent. > >>> > >>> > >>> On 21 February 2013 17:32, Jan Lehnardt wrote: > >>> > >>>> > >>>> On Feb 21, 2013, at 18:29 , Noah Slater wrote: > >>>> > >>>>> Your response rests on a fallacy, in any case. > >>>>> > >>>>> Maintaining a list of release versions is going to be a PITA no > matter > >>>> what > >>>>> we do. Especially when we have four or five divergent timelines. > Moving > >>>>> these to the docs only consolidates the maintenance into one file. > This > >>>>> will still require care and attention, and I believe it is > appropriate > >> of > >>>>> me to remind people of that. The current state of affairs is a > complete > >>>>> mess. > >>>> > >>>> All I know is we spend hours and days on this each release and I don= =92t > >>>> think this needs to be the case. > >>>> > >>>> Best > >>>> Jan > >>>> -- > >>>> > >>>> > >>>> > >>>>> > >>>>> > >>>>> On 21 February 2013 17:19, Jan Lehnardt wrote: > >>>>> > >>>>>> > >>>>>> On Feb 21, 2013, at 18:16 , Noah Slater wrote= : > >>>>>> > >>>>>>> Hi, > >>>>>>> > >>>>>>> If you're doing a release, please ensure proper NEWS and CHANGES > >>>> hygiene > >>>>>>> The recent releases went out with a entries in these files for > >> versions > >>>>>> we > >>>>>>> have not yet released. And some are missing entries for previous > >>>> versions > >>>>>>> we have released. I have added a few additional instructions to t= he > >>>> wiki, > >>>>>>> so hopefully these will be caught next time. > >>>>>> > >>>>>> Alternatively, let=92s finally kill this superfluous, error-prone, > >>>>>> time-wasting > >>>>>> distraction from actual work and ensure the important information > >>>> contained > >>>>>> in it are covered in the docs. > >>>>>> > >>>>>> Cheers > >>>>>> Jan > >>>>>> -- > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> NS > >>>> > >>>> > >>> > >>> > >>> -- > >>> NS > >> > >> > > > > > > -- > > NS > > --=20 NS --e89a8f22c6818f3cc304d6400911--