Wei, The build was made after this commit 55c56b6cc26d4e1f5156b0a6a387594659d271f5 . I think the commit that I put in the e-mail is the one that was generated by the script and unfortunately that I did not push. That generally results in two commits one with bumping the version and another with a revert of that. That is a reason enough for a respin or can we live with that for this release.
For second issue the bug seems to be resolved. And I see the right version in pom.xml, am I missing something here ? -abhi On 12/12/13 10:00 pm, "Wei ZHOU" <ustcweiz...@gmail.com> wrote: >Abhi, >I have two problems >(1) I can not checkout the commit >43350d64ce66e366f08a9fa13ad09bca462b66da, >it looks not exist >(2) the xapi version in deps/XenServerJava/pom.xml should not be changed >when you bump the version from 4.2.1-SNAPSHOT to 4.2.1. (see >CLOUDSTACK-4827) > >-Wei > > > >2013/12/10 Abhinandan Prateek <abhinandan.prat...@citrix.com> > >> Hi, >> >> This release candidate addresses the following additional issues >> reported by community: >> >> 1. CLOUDSTACK-5145 : ListNetworkACL API should list ACLs owned by the >>user >> only >> 2. CLOUDSTACK-5214 : 4.2.1 upgrade is broken >> 3. The CHANGES file has been fixed to mark some important fixes as such, >> instead of new features which they are not. >> >> The details of this RC are as: >> >> >>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=ref >>s/ >> heads/4.2 >> commit: 43350d64ce66e366f08a9fa13ad09bca462b66da >> >> List of changes are available in Release Notes, a summary can be >>accessed >> in CHANGES file: >> >>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=C >>HA >> NGES;hb=4.2 >> >> Source release revision 3865 (checksums and signatures are available at >> the same location): >> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.1/ >> **note that for release notes separate email will go out subsequently. >> >> PGP release keys (signed using RSA Key ID = 42443AA1): >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS >> >> Vote will be open for 72 hours (until 12/05 End of day PST). >> >> For sanity in tallying the vote, can PMC members please be sure to >> indicate "(binding)" with their vote? >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> >> >>
