Le 4/25/12 1:17 PM, Simone Tripodi a écrit :
Hi all,
I am a little confused on how you intend to manage the RC: let's say
development is X.Y, I would have *tagged* the X.Y-RCn for the n-th
candidate to vote the X.Y *release*, while I surprisingly see X.Y-RCn
as release... do you intend follow a cycle of X.Y-RCs, and then a
final X.Y-GA?
RC is a release (candidate :). I think it's named 'release' to follow
the ASF naming of what is a 'release' : a voted source tarball.
To me, 1.0.0-RC1 is a much a release a 1.0.0.
Anyway, my current position is +0 (it could become +1 while addressed
the following concerns) and here are my statements:
* build is not portable, or at least some guidelines would help to
address potential issues - once checked out the tag and launched the
install goal
+----+
svn co
https://svn.apache.org/repos/asf/incubator/syncope/tags/syncope-1.0.0-RC1-incubating/
\
cd syncope-1.0.0-RC1-incubating/ \
mvn install
+----+
I got the following error:
+----+
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Syncope .................................... SUCCESS [26.686s]
[INFO] Apache Syncope Build Tools ........................ SUCCESS [20.585s]
[INFO] Apache Syncope Client ............................. SUCCESS [11.328s]
[INFO] Apache Syncope Core ............................... FAILURE [20.838s]
[INFO] Apache Syncope Console ............................ SKIPPED
[INFO] Apache Syncope Root ............................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
Hmmm... I did that, but got a success... I also doomed my maven repo
before doing a mvn clean install.
$ mvn clean install
...
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Syncope .................................... SUCCESS
[3:54.242s]
[INFO] Apache Syncope Build Tools ........................ SUCCESS
[1:18.744s]
[INFO] Apache Syncope Client ............................. SUCCESS [20.857s]
[INFO] Apache Syncope Core ............................... SUCCESS
[6:50.362s]
[INFO] Apache Syncope Console ............................ SUCCESS [23.694s]
[INFO] Apache Syncope Root ............................... SUCCESS [0.005s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 12:50.246s
[INFO] Finished at: Wed Apr 25 14:05:03 CEST 2012
[INFO] Final Memory: 48M/125M
[INFO]
------------------------------------------------------------------------
$ mvn --version
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: /opt/maven-3.0.4
Java version: 1.6.0_31, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.7.3", arch: "x86_64", family: "mac"
* distribution package should contain RELEASE-NOTES (copied fom Jira is
enough)
That's not required, but it's useful.
Even if fixing current release lacks would be easy, I'd suggest you
anyway to roll an RC2 to have a better release process.
Here, I would disagree : if you don't provide a RC1 to download, people
will wonder where the hell is RC1...
IMHO, when the release is not voted, or withdrawn, then we should keep
the same number for the next attempt.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
