cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From runseb <>
Subject [GitHub] cloudstack pull request: 4.5 Branch: update pom version and add up...
Date Wed, 11 Mar 2015 16:33:03 GMT
Github user runseb commented on the pull request:
    On Mar 11, 2015, at 5:09 PM, Rohit Yadav <> wrote:
    > @runseb the bugs were fixed on 4.5 branch so they are already in 4.5 branch. I think
to create 4.5.1 RC one could simply branch off from 4.5 once these commits are merged, or
do you only want to create a different branch with only the identified critical bugfixes?
    > These are the list of important commits IMO that went into 4.5 branch but did n't
made into 4.5.0:
    So let me show my ignorance here.
    4.5.0 is a tag in the 4.5 branch ? correct ?
    Commits were made on top of that to fix some issues including a critical bug fix in 4.5.0
that is forcing us to release 4.5.1 quickly.
    Why don't we do a linear release on the 4.5 branch ? Why do you want to branch from 4.5
    In the end we vote on a git hash.
    > 02cadc3
    > f3f47f2
    > f9090ea
    > b2b9de7
    > b879916
    > ab8f367
    > 729e239
    > �
    > Reply to this email directly or view it on GitHub.

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 or file a JIRA ticket
with INFRA.

View raw message