Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
In-Reply-To: 
 <CADENRmqQWvqD8+GN1H0LQg=WpJ1CV=gHYoG-Pi5MxVeeptOeEg@mail.gmail.com>
References: <3E4C94CF-03F1-409F-A629-627DAC053402@gmail.com>
 <CEAB145F.47A53%abhinandan.prateek@citrix.com>
 <C3637609BC1C0D40A2AC70F4760C7A2D1AB986@SJCPEX01CL02.citrite.net>
 <CADENRmrQrfLOVKX7b=CPbtV=QSDy5uQvBL5YOW4oNzC4M3Y-QA@mail.gmail.com>
 <CAKprHVbXPt5NM2+1ZfdQQN_SQmi1Sp=J3ghHGz_JKGjgrFvRmQ@mail.gmail.com>
 <CAGQtxvbRUVdc8TfTB3mNQ_fxkMVryVue9rLWt+4b=LFji7=mxA@mail.gmail.com>
 <CADENRmqQWvqD8+GN1H0LQg=WpJ1CV=gHYoG-Pi5MxVeeptOeEg@mail.gmail.com>
From: David Nalley <david@gnsa.us>
Date: Thu, 14 Nov 2013 17:17:18 -0500
Message-ID: 
 <CAKprHVbb2S+uQ56T3sQqT9S_O4exonqUaMD-OQpgyu=UpLsBBg@mail.gmail.com>
Subject: Re: [ASF4.2.1] Release Notes
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Yes - no rule. That said, there is common sense. Releasing without
docs doesn't make a lot of sense. I am still trying to understand the
urgency of releasing.

--David

On Thu, Nov 14, 2013 at 5:12 PM, Chip Childers <chipchilders@apache.org> wr=
ote:
> There is absolutely no ASF rule or policy on this.  It's up to
> projects to decide things like "what's in the release".
>
> On Thu, Nov 14, 2013 at 5:11 PM, Daan Hoogland <daan.hoogland@gmail.com> =
wrote:
>> I can't imagine there not being some guideline or rule about providing
>> documentation in the apache foundation. Can we even release without docs=
,
>> not that we should. My idea was that we release on wednesday with the do=
cs
>> in rc state. Even that is, admitted, dubious.
>>
>> mobile biligual spell checker used
>> Op 14 nov. 2013 22:50 schreef "David Nalley" <david@gnsa.us>:
>>
>>> I agree - announcing a release prior to docs availability hurts the
>>> project because users fail in installation and upgrades.
>>> The gate in my mind is docs readiness - thats an integral part of the
>>> release process, even if the repo is separate.
>>>
>>> Animesh, whats your reason to want to push this out earlier?
>>>
>>> --David
>>>
>>> On Thu, Nov 14, 2013 at 4:20 PM, Chip Childers <chipchilders@apache.org=
>
>>> wrote:
>>> > Except that the separation only helps if it allows RC testing + votin=
g
>>> > during doc finalization.  If we announce before docs, it hurts us.
>>> > I'm against another announcement that goes out with the docs in poor
>>> > shape.
>>> >
>>> > On Thu, Nov 14, 2013 at 3:44 PM, Animesh Chaturvedi
>>> > <animesh.chaturvedi@citrix.com> wrote:
>>> >> Unless there are objection to the RC, I would prefer to have it
>>> released and make the announcement sooner and showcase in collab
>>> conference. As Chip mentions docs were broken out separately anyway.
>>> >>
>>> >> Animesh
>>> >>
>>> >>
>>> >> On 14/11/13 8:12 pm, "Sebastien Goasguen" <runseb@gmail.com> wrote:
>>> >>
>>> >>>Anyway we can wait next week to release.
>>> >>>
>>> >>>quite a few of us will be together in Amsterdam, we can dedicate a
>>> >>>hackathon session to 4.2.1 , make sure RN are good, upgrade path
>>> >>>etc=C5=A0then test=C5=A0.
>>> >>>
>>> >>>I'd recommend keeping the vote open until then.
>>> >>>
>>> >>>-sebastien
>>> >>>
>>> >>>
>>> >>>On Nov 14, 2013, at 5:57 AM, Radhika Puthiyetath
>>> >>><radhika.puthiyetath@citrix.com> wrote:
>>> >>>
>>> >>>> Hi,
>>> >>>>
>>> >>>> The master has the most up-to-date RN for 4.2.1.
>>> >>>>
>>> >>>> From: Abhinandan Prateek
>>> >>>> Sent: Thursday, November 14, 2013 2:22 PM
>>> >>>> To: CloudStack Dev
>>> >>>> Cc: Radhika Puthiyetath
>>> >>>> Subject: Re: [ASF4.2.1] Release Notes
>>> >>>>
>>> >>>>
>>> >>>> It seems the upgrade section of release notes will require a revie=
w,
>>> >>>>probably followed by a revamp (?).
>>> >>>> Can we have some volunteers who are familiar with various upgrade
>>> >>>>paths comment on it ?
>>> >>>> Me and Radhika will try to consolidate those comments, snippets an=
d
>>> >>>>fix the RN for 4.2.1.
>>> >>>>
>>> >>>> -abhi
>>> >>>>
>>> >>>> RN for 4.2.1 =3D
>>> >>>>https://git-wip-us.apache.org/repos/asf?p=3Dcloudstack-docs.git;a=
=3Dtree;f
>>> >>>>=3Dre
>>> >>>>lease-notes;h=3D8128d62c39236331492f3642914bf97b43ed2670;hb=3Drefs/=
heads/4
>>> >>>>.2
>>> >>>>
>>> >>>
>>> >>
>>>