[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cf-dev] Release new milestone
|
I created and pushed a tag "1.0.0-RC1" to have a reference to get the release review started.
Due to the open issues in the release process, I did not deploy the artifacts!
If anyone wants to use them (which you should not, because they are for reviewing only), you have to build install them locally from a cloned repo.
Ciao
Matthias
> -----Original Message-----
> From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Kovatsch Matthias
> Sent: Mittwoch, 14. Oktober 2015 19:35
> To: Californium (Cf) developer discussions <cf-dev@xxxxxxxxxxx>
> Cc: mikael@xxxxxxxxxxx
> Subject: Re: [cf-dev] Release new milestone
>
> Hi all
>
> Kai and I looked at the release build through Hudson. The following issues
> popped up:
>
> - Our HIPP needs to be able to write to GitHub to push the release version
> and tag and next version
> - The deploy goal needs both settings, for the Eclipse repo and for Maven
> Central (maybe that is possible by setting both "Settings" and "Global
> settings"; otherwise, we might need to put both settings in our project-
> specific settings.xml)
> - We want to deploy only when also the version update to next version and
> the push to GitHub was successful (otherwise there might be a half-baked
> deployment that needs manual resolution, for instance when someone
> pushes to GitHub while the release build is running on Hudson)
> - "mvn versions:set -DnewVersion=..." does not work anymore, since the
> components inherit from parent, but are in different repos :(
>
> Mikael, can you comment if you could enable a push from Hudson to GitHub?
>
> Ciao
> Matthias
> _______________________________________________
> cf-dev mailing list
> cf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit https://dev.eclipse.org/mailman/listinfo/cf-dev