You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by Kevan Miller <ke...@gmail.com> on 2009/04/01 06:33:35 UTC
Re: VCL release process VCL 2.1
On Mar 30, 2009, at 11:42 AM, Aaron Peeler wrote:
> Mentors,
>
> What are the steps for cutting a release?
>
> I think/suggest that by the end-of April(or sooner) we will have
> enough committed changes to create the release of VCL 2.1
See http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
and http://incubator.apache.org/guides/releasemanagement.html
You should plan on the initial release process being difficult and
time consuming...
I expect that we'll need to resolve the naming issue, prior to a
release. To this end, we might want to gather additional information/
opinions from either general@incubator.apache.org or legal-discuss@apache.org
.
--kevan
Re: VCL release process VCL 2.1
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kevan,
Things for pinging the list about this. We've just been trying to get all of
the JIRA issues on the 2.1 roadmap closed and finish defining the process at
http://cwiki.apache.org/VCL/cutting-a-vcl-release.html
We're almost there. I'll try to get a message posted today asking for input
on how to handle release candidates (the only TODO left on the above page).
I'm planning on being the release manager. I've created a GPG code signing
key. What's the best/easiest way to get into the ASF WOT? Should I try to
meet with Matt to get him to sign it? Any idea if there's someone at NCSU in
the ASF WOT already that could sign it?
Thanks,
Josh
On Friday September 18, 2009, Kevan Miller wrote:
> I haven't seen much in the way of release discussions recently.
>
> A primary goal for this community should be to graduate from the
> Incubator. Generating a release is going to be an important step in
> this graduation process.
>
> --kevan
- --
- -------------------------------
Josh Thompson
Systems Programmer
Advanced Computing | VCL Developer
North Carolina State University
Josh_Thompson@ncsu.edu
919-515-5323
my GPG/PGP key can be found at pgp.mit.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFKs5WBV/LQcNdtPQMRAtS8AJ95D750Y1i/5Bq43JidwbbfG1W93gCeMbo+
8y2qL8JlcL0JKKqn3BCaArg=
=YL0K
-----END PGP SIGNATURE-----
Re: VCL release process VCL 2.1
Posted by Kevan Miller <ke...@gmail.com>.
I haven't seen much in the way of release discussions recently.
A primary goal for this community should be to graduate from the
Incubator. Generating a release is going to be an important step in
this graduation process.
--kevan
Re: VCL release process VCL 2.1
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday April 01, 2009, Kevan Miller wrote:
> On Mar 30, 2009, at 11:42 AM, Aaron Peeler wrote:
> > Mentors,
> >
> > What are the steps for cutting a release?
> >
> > I think/suggest that by the end-of April(or sooner) we will have
> > enough committed changes to create the release of VCL 2.1
>
> See http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> and http://incubator.apache.org/guides/releasemanagement.html
>
> You should plan on the initial release process being difficult and
> time consuming...
>
> I expect that we'll need to resolve the naming issue, prior to a
> release. To this end, we might want to gather additional information/
> opinions from either general@incubator.apache.org or
> legal-discuss@apache.org .
I thought I'd start things moving toward a release again. I've been reading
over the 2 URLs Kevan listed above and started working on a page in
confluence for cutting a VCL release:
http://cwiki.apache.org/confluence/display/VCL/Cutting+a+VCL+Release
There's a concept of a "release manager" who is the person to spearhead
getting a release cut and who takes care of signing (with GPG) the release.
I'm willing to be this person this time around unless someone else would
really like to.
Hopefully, the recently revived name discussion will get the project name
established by the time everything else is ready for cutting a release.
Josh
- --
- -------------------------------
Josh Thompson
Systems Programmer
Virtual Computing Lab (VCL)
North Carolina State University
Josh_Thompson@ncsu.edu
919-515-5323
my GPG/PGP key can be found at pgp.mit.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFKAI6iV/LQcNdtPQMRAgTxAJ90PFDZb8Y5fJkSx1Ukdrvi84VLwACfdpC5
SxYvM4UnSZi4WDZJ1LfwKCs=
=uy1s
-----END PGP SIGNATURE-----