You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucy.apache.org by Apache Wiki <wi...@apache.org> on 2010/12/13 04:12:05 UTC
[lucy-commits] [Lucy Wiki] Update of "ReleaseGuide" by PeterKarman
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Lucy Wiki" for change notification.
The "ReleaseGuide" page has been changed by PeterKarman.
The comment on this change is: updates to reflect versioning decision and build structure (svn export | tar | gz).
http://wiki.apache.org/lucy/ReleaseGuide?action=diff&rev1=4&rev2=5
--------------------------------------------------
and publish your key at http://pgp.mit.edu/. For more details on signing releases, see [http://www.apache.org/dev/release-signing.html Signing Releases] and [http://www.apache.org/dev/mirror-step-by-step.html?Step-By-Step Step-By-Step Guide to Mirroring Releases].
+ = Versioning =
+
+ Apache Lucy uses the following X.Y.Z versioning scheme:
+ {{{
+ ASF release => lucy-0.2.0-incubating.tar.gz
+ CPAN release => Lucy-0.2.0.1.tar.gz
+ Documentation => 0.2.0.1
+ META.yml => 0.002000001
+ $VERSION => "0.002000001"
+ }}}
+
+ See the discussion [[http://mail-archives.apache.org/mod_mbox/incubator-lucy-dev/201012.mbox/browser|here]].
= Branching =
@@ -21, +33 @@
1. Notify developers on the #lucy_dev IRC channel that you are about to branch a release.
- 2. In trunk, update the CHANGES file with the release date (if known) and bump the $VERSION value to xxxxxxTODO.
+ 2. In trunk, update the CHANGES file with the release date (if known) and bump the $VERSION value to X.Y.Z.
3. Commit your changes to trunk.
{{{
- svn commit -m "Updating CHANGES and VERSION for release xxxxxxTODO"
+ svn commit -m "Updating CHANGES and VERSION for release X.Y.Z"
}}}
4. Create a branch for the release series:
{{{
svn copy https://svn.apache.org/repos/asf/incubator/lucy/trunk \
- https://svn.apache.org/repos/asf/incubator/lucy/branches/branch-xxxxxxTODO -m "Branching for xxxxxxTODO release"
+ https://svn.apache.org/repos/asf/incubator/lucy/branches/branch-X.Y.Z -m "Branching for X.Y.Z release"
}}}
= Building =
- 1. Check out a clean copy of the release branch:
+ 1. Export out a clean copy of the release branch:
{{{
- svn co https://svn.apache.org/repos/asf/incubator/lucy/branches/branch-xxxxxxTODO
+ svn export https://svn.apache.org/repos/asf/incubator/lucy/branches/branch-X.Y.Z
}}}
- 2. Build the Perl distribution (TODO other language bindings here):
+ 2. Tar and gzip the export:
{{{
+ tar -cf lucy-X.Y.Z-incubating.tar branch-X.Y.Z
+ gzip lucy-X.Y.Z-incubating.tar
- cd branch-xxxxxxTODO
- perl Build.PL
- ./Build dist
}}}
3. Perform whatever quality control seems prudent on the .tar.gz file, installing it on test system(s), etc.
4. Generate a MD5 checksum of the release file:
{{{
- md5sum apache-lucy-xxxxxxTODO.tar.gz > apache-lucy-xxxxxxTODO.tar.gz.md5
+ md5sum lucy-X.Y.Z-incubating.tar.gz > lucy-X.Y.Z-incubating.tar.gz.md5
}}}
5. Sign the release:
{{{
- gpg --armor --output apache-lucy-xxxxxxTODO.tar.gz.asc --detach-sig apache-lucy-xxxxxxTODO.tar.gz
+ gpg --armor --output lucy-X.Y.Z-incubating.tar.gz.asc --detach-sig lucy-X.Y.Z-incubating.tar.gz
}}}
6. Copy the release files to a public location:
{{{
- ssh people.apache.org mkdir public_html/apache-lucy-xxxxxxTODO-candidate-0
+ ssh people.apache.org mkdir public_html/lucy-X.Y.Z-incubating-candidate-0
- scp -p apache-lucy-xxxxxxTODO.tar.gz* people.apache.org:~/public_html/apache-lucy-xxxxxxTODO-candidate-0
+ scp -p lucy-X.Y.Z-incubating.tar.gz* people.apache.org:~/public_html/lucy-X.Y.Z-incubating-candidate-0
}}}
(TODO: do we stage to maven repository like Hadoop does (the example I'm following here))
Re: [lucy-dev] ReleaseGuide wiki and version numbering format
Posted by Peter Karman <pe...@peknet.com>.
Marvin Humphrey wrote on 12/14/10 6:28 PM:
> Peter Karman edited the wiki:
>
>> + Apache Lucy uses the following X.Y.Z versioning scheme:
>> + {{{
>> + ASF release => lucy-0.2.0-incubating.tar.gz
>> + CPAN release => Lucy-0.2.0.1.tar.gz
>> + Documentation => 0.2.0.1
>> + META.yml => 0.002000001
>> + $VERSION => "0.002000001"
>> + }}}
>> +
>> + See the discussion [[http://mail-archives.apache.org/mod_mbox/incubator-lucy-dev/201012.mbox/browser|here]].
>
> Just so we're on the same page...
>
> I was imagining that the first CPAN release for Lucy 0.2.0 would also be
> called "0.2.0", and that we'd only create a CPAN release called "0.2.0.1" if
> we botched "0.2.0". To me, the chart above implies that you expect the ASF
> release and the initial CPAN release to have different version numbers from
> the get go. Am I grokking you right?
>
ah no. We are imagining the same thing. My copy/paste does imply differently
though. I'll amend it.
--
Peter Karman . http://peknet.com/ . peter@peknet.com
[lucy-dev] ReleaseGuide wiki and version numbering format
Posted by Marvin Humphrey <ma...@rectangular.com>.
Peter Karman edited the wiki:
> + Apache Lucy uses the following X.Y.Z versioning scheme:
> + {{{
> + ASF release => lucy-0.2.0-incubating.tar.gz
> + CPAN release => Lucy-0.2.0.1.tar.gz
> + Documentation => 0.2.0.1
> + META.yml => 0.002000001
> + $VERSION => "0.002000001"
> + }}}
> +
> + See the discussion [[http://mail-archives.apache.org/mod_mbox/incubator-lucy-dev/201012.mbox/browser|here]].
Just so we're on the same page...
I was imagining that the first CPAN release for Lucy 0.2.0 would also be
called "0.2.0", and that we'd only create a CPAN release called "0.2.0.1" if
we botched "0.2.0". To me, the chart above implies that you expect the ASF
release and the initial CPAN release to have different version numbers from
the get go. Am I grokking you right?
Marvin Humphrey