jclouds-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Phillips <aphill...@qrmedia.com>
Subject Re: [VOTE] Release Apache jclouds 1.6.1-incubating, RC2
Date Sat, 01 Jun 2013 11:27:34 GMT
Any reason why this time we have a "prepare for release" commit [1]  
and then, a couple of commits later (but not immediately afterwards),  
a revert of that commit [2]?

I'm comparing it here to the "jclouds-1.6.1-incubating-rc0" tag [3],  
which was also a "prepare for release" commit, but which isn't in the  
1.6.x tree and wasn't reverted.

Also, assuming the prepare-then-revert model is the correct way to go,  
should the revert come immediately after the "prepare" commit?

Thanks!

ap

[1]  
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=commit;h=57718280be4bccea9e7885c5c3c38550f818d0dd
[2]  
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=commit;h=7828eef35957cbbb53b8ffd934c778fbe07dacc2
[3]  
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=commit;h=d99dae8c1c7b0a311f094bcd8ad5bfb1975fffb1

Mime
View raw message