Yes, this commit probably shouldn't have gone to master...
Can one of the commiters revert it?
Now, for the RC2, we will probably need to make the RC based on the
commit
hash from the top of the 0.12 branch and do a little
investigation/research
if there is any other changes to make the release prepare to modify the
pom
from the branch and google is probably your friend here.
Not sure what you mean here - can't we tag a new release candidate on
the branch-0.12? What (except for the tag) would have to change in the
pom?
-Felix
Am 21.01.2017 00:56 schrieb Luciano Resende:
I just saw a commit into master :
[maven-release-plugin] prepare release v0.12.0-incubating-rc2” --tag
Please be very careful with what we are trying to do. After 0.12 RC, we
have moved the development of 0.12 wich is based on Spark 1.6.x to a
0.12
branch, but the commit info above makes me think that we are trying to
cut
a 0.12 RC2 from master which then will bring the Spark 2.0 support
which is
not desirable and is scheduled for 0.12.
Also note that master is now in a corrupted state, where the pom is
corrupted (particularly the scmelement)
<scm> <connection>scm:git:g...@github.com:apache/incubator-systemml</
connection> <developerConnection>scm:git:
https://git-wip-us.apache.org/repos/asf/incubator-systemml</
developerConnection> <url>
https://git-wip-us.apache.org/repos/asf?p=incubator-systemml.git</url>
<tag>v0.12.0-incubating-rc2”
--tag</tag> </scm>
Please revert the commit in master
(083c9c4ca0bc3deeb04f2552470a9e187b80bcf4)
Now, for the RC2, we will probably need to make the RC based on the
commit
hash from the top of the 0.12 branch and do a little
investigation/research
if there is any other changes to make the release prepare to modify the
pom
from the branch and google is probably your friend here.
