You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by David Lutterkort <lu...@redhat.com> on 2010/10/30 00:12:53 UTC
RELEASE: rc1 uploaded
Hi,
to get the process of making a formal release started, I just uploaded
artifacts for a deltacloud 0.1.0 release. The artifacts were built from
git commit 231153b8 - once we have a formal release, I will also tag it
in svn.
The release consists of four files total: the server and the Ruby
client, in gem and tgz format each. It can be found at [1]. There is
also a detached GPG signature for each of the files[2]
I'd appreciate any feedback on the release candidate; if you find
bugs/issues, please speak up on this list. I'd also appreciate any
guidance on what steps or artifacts are missing from the release
candidate.
My understanding of the process is that I need to call for a vote on the
general@ mailing list. If nobody on this list objects, I'd like to start
that process on Monday.
David
[1] http://people.apache.org/~lutter/deltacloud/0.1.0/rc1/
[2] To verify the signature, first download both the .sig file and the
corresponding artifact. Then, run a command like this:
gpg --verify $artifact.sig
If that command fails because you don't have the required public key,
then run this command to import it:
gpg --keyserver keys.gnupg.net --recv-keys FC6E8A22
and rerun the `gpg --verify' command.
Re: RELEASE: rc1 uploaded
Posted by Carl Trieloff <cc...@redhat.com>.
On 10/29/2010 06:47 PM, Luciano Resende wrote:
> On Fri, Oct 29, 2010 at 3:12 PM, David Lutterkort<lu...@redhat.com> wrote:
>
>> Hi,
>>
>> to get the process of making a formal release started, I just uploaded
>> artifacts for a deltacloud 0.1.0 release. The artifacts were built from
>> git commit 231153b8 - once we have a formal release, I will also tag it
>> in svn.
>>
>> The release consists of four files total: the server and the Ruby
>> client, in gem and tgz format each. It can be found at [1]. There is
>> also a detached GPG signature for each of the files[2]
>>
>>
> Do we need .asc and .md5 files for each of the artifacts as well ?
>
yes the release needs to be signed
>
>> I'd appreciate any feedback on the release candidate; if you find
>> bugs/issues, please speak up on this list. I'd also appreciate any
>> guidance on what steps or artifacts are missing from the release
>> candidate.
>>
>> My understanding of the process is that I need to call for a vote on the
>> general@ mailing list. If nobody on this list objects, I'd like to start
>> that process on Monday.
>>
>>
> The process is that the RM call a vote on the dev list, where
> committers would review and vote. While the project is still in
> incubation, we need a second round of vote in general@, but that only
> happens after the vote is passed here.
>
>
>
>
Re: RELEASE: rc1 uploaded
Posted by David Lutterkort <lu...@redhat.com>.
On Fri, 2010-10-29 at 15:47 -0700, Luciano Resende wrote:
> On Fri, Oct 29, 2010 at 3:12 PM, David Lutterkort <lu...@redhat.com> wrote:
> > Hi,
> >
> > to get the process of making a formal release started, I just uploaded
> > artifacts for a deltacloud 0.1.0 release. The artifacts were built from
> > git commit 231153b8 - once we have a formal release, I will also tag it
> > in svn.
> >
> > The release consists of four files total: the server and the Ruby
> > client, in gem and tgz format each. It can be found at [1]. There is
> > also a detached GPG signature for each of the files[2]
> >
>
> Do we need .asc and .md5 files for each of the artifacts as well ?
I don't have strong opinions on that - I just removed the .sig file and
replaced them with .asc files; I also added a MD5SUM and a SHA1SUM file.
> > I'd appreciate any feedback on the release candidate; if you find
> > bugs/issues, please speak up on this list. I'd also appreciate any
> > guidance on what steps or artifacts are missing from the release
> > candidate.
> >
> > My understanding of the process is that I need to call for a vote on the
> > general@ mailing list. If nobody on this list objects, I'd like to start
> > that process on Monday.
> >
>
> The process is that the RM call a vote on the dev list, where
> committers would review and vote. While the project is still in
> incubation, we need a second round of vote in general@, but that only
> happens after the vote is passed here.
Ok .. then I'll send a separate mail calling for a vote here.
David
Re: RELEASE: rc1 uploaded
Posted by Luciano Resende <lu...@gmail.com>.
On Fri, Oct 29, 2010 at 3:12 PM, David Lutterkort <lu...@redhat.com> wrote:
> Hi,
>
> to get the process of making a formal release started, I just uploaded
> artifacts for a deltacloud 0.1.0 release. The artifacts were built from
> git commit 231153b8 - once we have a formal release, I will also tag it
> in svn.
>
> The release consists of four files total: the server and the Ruby
> client, in gem and tgz format each. It can be found at [1]. There is
> also a detached GPG signature for each of the files[2]
>
Do we need .asc and .md5 files for each of the artifacts as well ?
> I'd appreciate any feedback on the release candidate; if you find
> bugs/issues, please speak up on this list. I'd also appreciate any
> guidance on what steps or artifacts are missing from the release
> candidate.
>
> My understanding of the process is that I need to call for a vote on the
> general@ mailing list. If nobody on this list objects, I'd like to start
> that process on Monday.
>
The process is that the RM call a vote on the dev list, where
committers would review and vote. While the project is still in
incubation, we need a second round of vote in general@, but that only
happens after the vote is passed here.
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/