incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <chip.child...@sungard.com>
Subject Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
Date Thu, 25 Oct 2012 19:01:48 GMT
On Thu, Oct 25, 2012 at 2:57 PM, Olivier Lamy <olamy@apache.org> wrote:
> 2012/10/25 Chip Childers <chip.childers@sungard.com>:
>> On Thu, Oct 25, 2012 at 4:28 AM, Olivier Lamy <olamy@apache.org> wrote:
>>> +1 (binding).
>>> I checked sigs, license headers: sounds good.
>>>
>>> A minor point is the KEYS file available here
>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS .
>>> Perso I would prefer to see it in a scm (most of Apache do that).
>>> Maybe for next release using svnpubsub for dist (at least it will be
>>> in svn and available with distrib)
>>> Let me know if I can help to setup this process.
>>
>> Oliver,
>>
>> Noah advised us to remove the KEYS file from our source tree earlier.
>>
>> I'll be putting it in the dist folder (URL will be
>> http://www.apache.org/dist/incubator/cloudstack/KEYS ).  My
>> understanding is that (after the IPMC vote) I simply copy the files
>> from my p.a.o public_html space to the correct folder on that server,
> correct
>> and then the mirrors start picking it up.  Is there actually an SVN
>> method of adding the artifacts to the dist folder?
> This need some setup first.
> Some projects commit rc builds to
> https://dist.apache.org/repos/dist/dev/ then once the vote has passed
> do a simple svn mv to https://dist.apache.org/repos/dist/release/
> (infra folks can setup a process to populate distribution folders from
> this svn path).
> A bit late now so for next release.

I requested this:  https://issues.apache.org/jira/browse/INFRA-5225

Advice on how to use it properly would be appreciated!

>>
>> -chip
>>
>>> 2012/10/22 Chip Childers (ASF) <chipchilders@apache.org>:
>>>> Hi All,
>>>>
>>>> I would like to call a vote for Apache CloudStack (Incubating) Release
>>>> 4.0.0-incubating (third round).
>>>>
>>>> We encourage the whole community to download and test these release
>>>> artifacts, so that any critical issues can be resolved before the
>>>> release is made. The more time that each individual spends reviewing
>>>> the artifacts, the higher confidence we can have in both the release
>>>> itself and our ability to pass an IPMC vote later on.  Everyone is free
>>>> to vote on this release, so please give it a shot.
>>>>
>>>> Instructions for Validating and Testing the artifacts can be found here:
>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>>>>
>>>> If you have any trouble setting up a test environment using the
>>>> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
>>>> will be sure to help, and we'll improve our test procedure
>>>> documentation at the same time!
>>>>
>>>> Now, on to the specifics of what we are voting on...
>>>>
>>>>
>>>> The following artifacts are up for the vote:
>>>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>>>>
>>>> PGP release keys (signed using A99A5D58):
>>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>>>
>>>> Branch: 4.0
>>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>>>
>>>>
>>>> List of changes:
>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>>>>
>>>> The artifacts being voted on during this round also include the
>>>> following additional fixes (most were identified as part of testing
>>>> during the last round of voting):
>>>>
>>>> * Many documentation fixes (particularly the release notes and
>>>> installation guide)
>>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
>>>> * CLOUDSTACK-349: Russian l10n not properly displaying
>>>> * Correction to the devcloud rdeploy build target, to make testing easier
>>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
>>>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>>>> * DISCLAIMER added to the Marvin tool dir
>>>>
>>>>
>>>> The vote will be open for 72 hours.
>>>>
>>>>
>>>> For sanity in tallying the vote, can PPMC and IPMC members please be
>>>> sure to indicate "(binding)" with their vote?
>>>> [ ] +1  approve
>>>> [ ] +0  no opinion
>>>> [ ] -1  disapprove (and reason why)
>>>>
>>>> Thanks!
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>

Mime
View raw message