On Wed, Jan 25, 2017 at 1:25 PM, wrote:
> Yeah as long as the branch is checked out with Git, Maven should work as
> intended.
>
>
Do you need to change the scm section in pom in any way ?
--
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
> Subject: Re: Building releases now that we have branches
>
>> On Fri, Jan 20, 2017 at 4:51 PM, wrote:
>>
>> Yes, this commit probably shouldn't have gone to master...
>> Can one of the commiters revert it?
>>
>>
> I would leave for the Release m
: Re: Building releases now that we have branches
On Fri, Jan 20, 2017 at 4:51 PM, wrote:
> Yes, this commit probably shouldn't have gone to master...
> Can one of the commiters revert it?
>
>
I would leave for the Release manager to revert it
> Now, for the RC2, we will p
On Fri, Jan 20, 2017 at 4:51 PM, wrote:
> Yes, this commit probably shouldn't have gone to master...
> Can one of the commiters revert it?
>
>
I would leave for the Release manager to revert it
> Now, for the RC2, we will probably need to make the RC based on the commit
>> hash from the top of
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
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
