cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daan Hoogland <>
Subject Re: implementing git workflow
Date Wed, 06 Aug 2014 06:05:31 GMT
I don't think we should hold on improving our way of working just
because it is not perfect yet. Some things are unclear so we can't do
those. Other things are perfectly clear and need to wait for nothing
else. That doesn't mean that a second vote isn't needed. It is if not
for anything else then for making sure we all want to go in the same
direction. I posted a lengthy reply on the vote thread to answer any
concerns and provoke more discussion. Let's see if that breeds further
ideas and then decide on a next phase/vote.

makes sense?

On Wed, Aug 6, 2014 at 6:23 AM, Rajani Karuturi
<> wrote:
> For a proposal which got all +1’s[1] what are the next steps to do?? It was made clear
on the voting thread that required branching changes would be done if the vote passes[2]
> Though the content in the document changed, the original proposal hasn’t changed. Its
still the same.
> It is explained in details with all the commands and more details in the wiki. Hence
there is quite a bit of text changes. It is not a diversion from what is already discussed.
> [1]
> [2]
> ~Rajani
> On 06-Aug-2014, at 12:56 am, David Nalley <<>>
> On Tue, Aug 5, 2014 at 2:51 PM, Alena Prokharchyk
> <<>> wrote:
> I think we should hold on with the git workflow implementation till all
> the decisions on the items written by Leo, are discussed and finalized.
> The very beginning of ³git workflow vote² shows that the vote was just to
> get people opinion on the proposal. Before adopting it and cutting the
> develop branch, all the questions should be cleared out.
> I agree with Alena - the vote was framed as opinion, not adoption.
> Moreover, the document voted on has been changed ~10 times since we
> started the vote, and the differences are substantial:
> Agreement to do something and the following implementation are not
> necessarily instantaneous.


View raw message