Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of terbolous@gmail.com designates
 209.85.214.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <C2CE0C2A-A949-4AB3-9AFD-F14EC8CFA539@apache.org>
References: <C2CE0C2A-A949-4AB3-9AFD-F14EC8CFA539@apache.org>
Date: Wed, 11 Jun 2014 18:43:31 +0200
Message-ID: 
 <CAP997UcH8_QOdNtsAwHrFL-Vi-mmid471CTSKAgXq4A0bu2S2A@mail.gmail.com>
Subject: Re: [DISCUSS] Release 4.4
From: Erik Weber <terbolous@gmail.com>
To: dev <dev@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2ec9afdae3604fb9224d7

--001a11c2ec9afdae3604fb9224d7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Jun 11, 2014 at 5:30 PM, Hugo Trippaers <hugo@apache.org> wrote:

> Hey all,
>
> I=E2=80=99m getting somewhat concerned about the 4.4 release. We don=E2=
=80=99t seems to be
> able to get the 4.4 branch in shape for a release candidate and meanwhile
> master is diverging further and further. We also know that once we hit th=
e
> RC phase we will probably need a sizable number of iterations to eventual=
ly
> ship the release. Based on past experience, if we keep up like this we wi=
ll
> have another release that will actually be released way after the feature
> freeze for the next release (July 18). Probably leaving us in the same ba=
d
> spot for the next release.
>
> I tried to come up with a number of solutions that could rectify the
> situation and help the release move forward, but i can=E2=80=99t think of=
 any. Save
> for some options that might be considered extreme ideas. One the the more
> prominent ideas in my mind at the moment is skipping the 4.4 release all
> together and combine it with the next planned release (whether its 5.0 or
> 4.5). This would require a community effort to focus on quality in the ne=
xt
> month and basically freeze the master for features and have a community
> wide push for quality to get the next release out on schedule.
>
>

What happens if that release doesn't make its desired time frame? Skip that
too and wait for 4.6 / 5.1 / 6.0?
If any drastic choices were to be made, I'd prefer that the next release
(4.5 / 5.0) either gets postponed, or skipped.
A major version bump with API changes could possibly warrant such drastic
change in my opinion.


> But before i go on and shout out even more drastic ideas, what do you
> think about the current 4.4 release. How close do you feel that we are to
> having a releasable product?
>
>
As a non developer I can only comment based on what I experience on the
mailing list, but this seems to be a repeating problem..
And something should probably be done to prevent this from being a / the
problem every release.


--=20
Erik Weber

--001a11c2ec9afdae3604fb9224d7--