You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@etch.apache.org by James Dixson <di...@gmail.com> on 2009/02/02 15:56:22 UTC
Release 1.0.2 Final Checklist
Ok, I think 1.0.2 is just about ready to go. I fixed the version
strings to report "apache-etch-1.0.2-incubating" in what seem to be
all the appropriate places, validated builds on linux, macosx, and
windows, and cleaned-up the build.txt and readme.txt files.
I am going to run a few more tests today and once I am finished 1.0.2
should be ready for release.
So...
To actually release something under apache there must be a process as
well as logististical tasks :-)
Here is what I think we still need to do/resolve:
1. Generate final binary/source images (should happen today)
2. Sign the images... easy enough, but what key should I use, or if I
use one of my keys, is there a standard place folks make their public
keys available?
3. Take a vote in etch-dev
4. Take a vote in incubator-dev
5. Publish the images... Q: where should/can the binaries be posted?
Am I missing anything?
--
james
Re: Release 1.0.2 Final Checklist
Posted by "scott comer (sccomer)" <sc...@cisco.com>.
we need to update the changelog one last time...
scott out
James Dixson wrote:
> Ok, I think 1.0.2 is just about ready to go. I fixed the version
> strings to report "apache-etch-1.0.2-incubating" in what seem to be
> all the appropriate places, validated builds on linux, macosx, and
> windows, and cleaned-up the build.txt and readme.txt files.
>
> I am going to run a few more tests today and once I am finished 1.0.2
> should be ready for release.
>
> So...
>
> To actually release something under apache there must be a process as
> well as logististical tasks :-)
>
> Here is what I think we still need to do/resolve:
>
> 1. Generate final binary/source images (should happen today)
> 2. Sign the images... easy enough, but what key should I use, or if I
> use one of my keys, is there a standard place folks make their public
> keys available?
> 3. Take a vote in etch-dev
> 4. Take a vote in incubator-dev
> 5. Publish the images... Q: where should/can the binaries be posted?
>
> Am I missing anything?
>
> --
> james
>
Re: Release 1.0.2 Final Checklist
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Mon, Feb 2, 2009 at 5:25 PM, James Dixson <di...@gmail.com> wrote:
> Thanks Niclas, that is what I was looking for.
Only trying to do my job as Mentor.
And while on the subject; I think this relatively homogeneous group of
people has so far progressed as good as the best projects in recent
Incubator history, such as Wicket, coming from already existing OSS
values and processes.
So, if we can attract more active developers then this incubation
period could be short. In fact, I would say that this 'reach out' is
paramount more important than code works beyond the 1.0.2 release, and
a requirement for graduation.
Cheers
Niclas
--
http://www.qi4j.org - New Energy for Java
Re: Release 1.0.2 Final Checklist
Posted by James Dixson <di...@gmail.com>.
Thanks Niclas, that is what I was looking for.
--
james
On Mon, Feb 2, 2009 at 10:00 AM, Niclas Hedhman <ni...@hedhman.org> wrote:
> On Mon, Feb 2, 2009 at 4:49 PM, Niclas Hedhman <ni...@hedhman.org> wrote:
>
>>> 2. Sign the images... easy enough, but what key should I use, or if I
>>> use one of my keys, is there a standard place folks make their public
>>> keys available?
>>
>> Well, many public PGP servers are used, such as pgp.mit.edu. More
>> importantly, they should also be stored in a KEYS file in the root of
>> the project.
>
> More info at http://www.apache.org/dev/release-signing.html
>
> Cheers
> Niclas
> --
> http://www.qi4j.org - New Energy for Java
>
Re: Release 1.0.2 Final Checklist
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Mon, Feb 2, 2009 at 4:49 PM, Niclas Hedhman <ni...@hedhman.org> wrote:
>> 2. Sign the images... easy enough, but what key should I use, or if I
>> use one of my keys, is there a standard place folks make their public
>> keys available?
>
> Well, many public PGP servers are used, such as pgp.mit.edu. More
> importantly, they should also be stored in a KEYS file in the root of
> the project.
More info at http://www.apache.org/dev/release-signing.html
Cheers
Niclas
--
http://www.qi4j.org - New Energy for Java
Re: Release 1.0.2 Final Checklist
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Mon, Feb 2, 2009 at 3:56 PM, James Dixson <di...@gmail.com> wrote:
> 1. Generate final binary/source images (should happen today)
Apache is all about Open Source, so the source distro is actually more
important than the binaries, from a legal point of view. Any artifact
being generated, need to have LICENSE and NOTICE files in them.
> 2. Sign the images... easy enough, but what key should I use, or if I
> use one of my keys, is there a standard place folks make their public
> keys available?
Well, many public PGP servers are used, such as pgp.mit.edu. More
importantly, they should also be stored in a KEYS file in the root of
the project.
> 3. Take a vote in etch-dev
Correct.
> 4. Take a vote in incubator-dev
If you mean general@incubator.apache.org - Correct. Typically,
announce on general@incubator.apache.org that there will be a vote
started on etch-dev a day in advance, so people can jump in if they
feel like it.
> 5. Publish the images... Q: where should/can the binaries be posted?
Yes, before the vote of course. Most people upload to their account on
people.apache.org. If you create a public_html folder, it will show up
as http://people.apache.org/~niclas
> Am I missing anything?
Yes, there is a tool called RAT. It will analyze the files from a
legal perspective and report any potential issues. The incubator PMC
members are typically keen on seeing its output.
http://incubator.apache.org/rat/
So, upload the rat output to people.apache.org as well.
Cheers
Niclas
--
http://www.qi4j.org - New Energy for Java