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 <chipchild...@apache.org> wrote: > 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.hoogl...@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 docs >> in rc state. Even that is, admitted, dubious. >> >> mobile biligual spell checker used >> Op 14 nov. 2013 22:50 schreef "David Nalley" <da...@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 <chipchild...@apache.org> >>> wrote: >>> > Except that the separation only helps if it allows RC testing + voting >>> > 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.chaturv...@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" <run...@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Šthen testŠ. >>> >>> >>> >>>I'd recommend keeping the vote open until then. >>> >>> >>> >>>-sebastien >>> >>> >>> >>> >>> >>>On Nov 14, 2013, at 5:57 AM, Radhika Puthiyetath >>> >>><radhika.puthiyet...@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 review, >>> >>>>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 and >>> >>>>fix the RN for 4.2.1. >>> >>>> >>> >>>> -abhi >>> >>>> >>> >>>> RN for 4.2.1 = >>> >>>>https://git-wip-us.apache.org/repos/asf?p=cloudstack-docs.git;a=tree;f >>> >>>>=re >>> >>>>lease-notes;h=8128d62c39236331492f3642914bf97b43ed2670;hb=refs/heads/4 >>> >>>>.2 >>> >>>> >>> >>> >>> >> >>>
