incubator-deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carl Trieloff <cctriel...@redhat.com>
Subject Re: [VOTE] release deltacloud 0.1.0
Date Tue, 07 Dec 2010 14:57:02 GMT
On 11/22/2010 08:23 AM, Carl Trieloff wrote:
> On 11/19/2010 12:29 PM, Luciano Resende wrote:
>> On Fri, Nov 19, 2010 at 5:48 AM, Carl 
>> Trieloff<cctrieloff@redhat.com>  wrote:
>>> Jim,
>>>
>>>   I remember at one point there was a discussion that if 3 mentors 
>>> +1'ed on
>>> this
>>> list, then the IPMC only needs to be notified. If there are not 3 
>>> member
>>> votes then
>>> the vote needs to be had on the incubator list. Did that discussion go
>>> anywhere
>>> (do you know)... i.e. if that is an option there are enough mentors 
>>> on the
>>> project
>>> to complete the vote on the dev list and we should ping the mentors.
>>>
>>> What is the current state on this in incubator?
>>> Carl.
>> While in Incubator, you need to request IPMC approval for releases. If
>> you already have the 3 binding IPMC votes, then it's just a matter of
>> waiting the 72hrs period in the general@ list.
>
>
> I've spent a bit of time looking through the release.
>
> Few issues:
>
> - It is common practice to have the ASL license header in the top of 
> all source
> files in the release. I would like to see that we follow that common 
> practice.
>
> For example server.ru and deltacloud.rb in the core package have no 
> license headers,
> the client tz seems to be much better applied with license headers 
> than core.
>
> - The release will also need to be signed to pass IPMC review.
>
> If the above two issues are resolved I'll +1 the release.
>
> Carl.
>
>
>


After some discussion with Jim, it is understood that we can add the 
headers in the
next release as we have the main license file. I'm thus placing my +1 vote.

+1 -- release deltacloud.

Carl.



Mime
View raw message