Thanks Roman,
As per the earlier thread (subject: releaseType?) and Spring conventions, it
seems that these milestone releases 'M#' come before release candidates 'RC#'
and not together M#.RC#. So the expected release progression is:
1.0.0-incubating.M1
1.0.0-incubating.M2
...
1.0.0-incubating.RC1
1.0.0-incubating.RC2
...
1.0.0-incubating.RELEASE
I think Greg had asked this question as well:
For such milestone releases, do we need to sign/vote/publish or should that be
done only for RC and RELEASE?
- Nitin
________________________________________
From: shaposh...@gmail.com <shaposh...@gmail.com> on behalf of Roman Shaposhnik
<ro...@shaposhnik.org>
Sent: Monday, January 11, 2016 9:06 PM
To: dev@geode.incubator.apache.org
Subject: A few recommendations on how to produce our first RC
Hi!
here's a few recommendation on how to
produce your first RC. Basically your MVP
of sorts should be the following set of files:
archive: geode-1.0.0-incubating.M1-src.tar.gz
GPG sig: geode-1.0.0-incubating.M1-src.tar.gz.asc
MD5 sum: geode-1.0.0-incubating.M1-src.tar.gz.md5
SHA sum: geode-1.0.0-incubating.M1-src.tar.gz.sha
in case you have strong feeling for publishing
zip/bz2 archive(s) instead (or in addition to)
more conventional tarballs -- that's fine.
Once you've generated the above 4 files the easiest
way to submit them for a vote and later allow for
RC -> release promotion is to check them into
the SVN dist folder corresponding to the RC ID. The first
RC being 1 (or 0 depending on whether you like
Algol 68 or C). E.g.:
https://dist.apache.org/repos/dist/dev/incubator/geode/1.0.0-incubating.M1.RC0
The dist.apache.org SVN is how ASF manages its
releases. Thus if the vote on the RC passes the promotion
of an RC candidate into an actual release becomes
a simple matter of
$ svn mv
Thanks,
Roman.
