cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rohit Yadav <>
Subject Re: [QUESTION] How come we don't include Users@ in vote threads?
Date Mon, 17 Nov 2014 07:24:55 GMT
My suggestions and comments;

- Build a rpm/deb repository before you start voting (we can use

- Tag each Voting Candidate (using a -vc or -rc suffix followed by the round number, for example
4.4.2-rc-01) and we build rpm/deb repo using tags.

- This repo can be used by both developers and users

- Let everyone participate, any contribution should we welcomed, so email all - dev@ and users@
and user-cn@. AFAIK, there is no *rule* stopping us from doing it so I recommend the release
manager should do it. Of course this has to be at their discretion and judgement.

- 72 hours (during weekdays, not weekends) limit should be good enough for everyone, by increasing
this limit we risk delaying the release. If a weekend lies in a voting window, historically
we've added additional weekend days as well, so the voting window can go upto 120 hours. Typically
I’ve seen 4 voting rounds for any release, that means delaying release by at least 3 weeks.
The other argument is, it may not be enough for developers as well. So, if you don’t find
it enough - you should start a new thread as I think it's a different topic than this email.

> On 17-Nov-2014, at 12:32 pm, Erik Weber <> wrote:
> On Sun, Nov 16, 2014 at 11:44 PM, Pierre-Luc Dion <>
> wrote:
>> I agree that more tests are welcome, we have to try then :)
> On the other side, how many devs can say that they really like to do
> thorough release testing? My guess is that it's a rather small number.
> By adding users, and if testing actually gains any momentum, you can
> hopefully have faith in that the release has been tested and free up some
> developer time to do more development :-)
> There's one thing that should be thought of though. Users might not pay
> attention to dev@ and might not know when to expect an RC.
> So I think a 72 hours time limit for users to test is gonna be to little,
> $dayjobs and personal lifes might not allow all to just throw whatever
> they're doing to start testing.
> I'm not sure what the best way to remedy it is, if it's to extend the time
> window or introduce another term/phase.
> --
> Erik

Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 |
Blog: | Twitter: @_bhaisaab

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build<>
CSForge – rapid IaaS deployment framework<>
CloudStack Consulting<>
CloudStack Software Engineering<>
CloudStack Infrastructure Support<>
CloudStack Bootcamp Training Courses<>

This email and any attachments to it may be confidential and are intended solely for the use
of the individual to whom it is addressed. Any views or opinions expressed are solely those
of the author and do not necessarily represent those of Shape Blue Ltd or related companies.
If you are not the intended recipient of this email, you must neither take any action based
upon its contents, nor copy or show it to anyone. Please contact the sender if you believe
you have received this email in error. Shape Blue Ltd is a company incorporated in England
& Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated
under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated
in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company
registered by The Republic of South Africa and is traded under license from Shape Blue Ltd.
ShapeBlue is a registered trademark.
View raw message