Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: bhaisaab <git@git.apache.org>
To: dev@cloudstack.apache.org
Reply-To: dev@cloudstack.apache.org
References: <git-pr-112-cloudstack@git.apache.org>
In-Reply-To: <git-pr-112-cloudstack@git.apache.org>
Subject: [GitHub] cloudstack pull request: 4.5 Branch: update pom version and
 add up...
Content-Type: text/plain
Message-Id: <20150312061101.E221BE18AC@git1-us-west.apache.org>
Date: Thu, 12 Mar 2015 06:11:01 +0000 (UTC)

Github user bhaisaab commented on the pull request:

    https://github.com/apache/cloudstack/pull/112#issuecomment-78429050
  
    @runseb So we've two options:
    
    I merge this into 4.5 and then a 4.5.1 RC1 candidate is cut off 4.5 branch. On 4.5 branch there aren't many commits that have went into after 4.5.0 was cut/released.
    
    Or,
    
    I merge this into 4.5 and share only commits that need to be picked on top of 4.5.0 (tag). That is - I'll create a branch from the 4.5.0 tag and cherry-pick commits that need to go into the emergency 4.5.1 and use that for voting?
    
    Which one do you prefer?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---