Re: [cf-dev] Deploy RC1 to eclipse releases repo

["Kovatsch Matthias" <kovatsch@xxxxxxxxxxx>]

Feel free to continue with RC2 and so on to test the release process from the current head. We had some updates since RC1 already (while not modifying any relevant stuff---Wayne said that is fine for the release process). Thanks for taking care of this!

I think it is also fine to trigger each sub-release on its own, that is, parent, element-connector, scandium, etc.

Ciao
Matthias


> -----Original Message-----
> From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Hudalla Kai (INST/ESY)
> Sent: Freitag, 30. Oktober 2015 10:23
> To: Californium (Cf) developer discussions
> Subject: Re: [cf-dev] Deploy RC1 to eclipse releases repo
> 
> Hi Matthias,
> 
> thanks for asking but it seems to be easier to run through this process alone
> for now. As a matter of fact I cannot use the fully automated release builds
> we have defined because they are designed to check out master's HEAD and
> create a release from that revision in one step as opposed to what we did
> with RC1, i.e. manually creating the TAG and then later build and release that
> revision.
> 
> From my point of view it is still desirable to be able to do the tagging and
> releasing in one automated build and I think we are on a good way of getting
> there. The only remaining concern I currently have is how to orchestrate the
> multiple (release) build jobs for releasing all Californium components
> together. But maybe that can be done using the Promoted Build plugin...
> 
> For now, I have created additional build jobs that check out a particular TAG
> and release the artifacts. But we will do this only for RC1 I hope. Thus, if we
> want to test our automated release process, we will need to create RC2
> some time soon ;-)
> 
> Regards,
> Kai
> 
> > -----Original Message-----
> > From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
> > On Behalf Of Kovatsch Matthias
> > Sent: Thursday, October 29, 2015 5:13 PM
> > To: Californium (Cf) developer discussions
> > Subject: Re: [cf-dev] Deploy RC1 to eclipse releases repo
> >
> > Hi Kai
> >
> > We should definitely start testing the release process. The release
> > review is ongoing and I think it looks good---Nov 4 we should release.
> >
> > Anything I can/should do? Change or check the *-release jobs on Hudson?
> >
> > Ciao
> > Matthias
> >
> > > -----Original Message-----
> > > From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
> > > On Behalf Of Hudalla Kai (INST/ESY)
> > > Sent: Donnerstag, 29. Oktober 2015 13:30
> > > To: Californium (Cf) developer discussions
> > > Subject: Re: [cf-dev] Deploy RC1 to eclipse releases repo
> > >
> > > Oh, I totally forgot that we cannot deploy to Eclipse's Release Repo
> > > using a manual build on private machines but only from out HIPP
> > infrastructure.
> > > Anyways, I would dare try to do this using our HIPP instance as well
> > > :-)
> > >
> > > Regards,
> > > Kai
> > >
> > >
> > > > -----Original Message-----
> > > > From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-
> > bounces@xxxxxxxxxxx]
> > > > On Behalf Of Hudalla Kai (INST/ESY)
> > > > Sent: Thursday, October 29, 2015 1:25 PM
> > > > To: Californium (Cf) developer discussions
> > > > Subject: [cf-dev] Deploy RC1 to eclipse releases repo
> > > >
> > > > Dear fellow committers,
> > > >
> > > > since people are already starting to complain why RC1 is not
> > > > available yet via Maven [1] ;-), I would like to (manually) create
> > a
> > > > release build of RC1 and deploy it to Eclipse's release repo [2]
> > > > using my personal GPG key (hopefully for the last time ;-)). We
> > > > can then later decide if we also want to make it available on
> > > > Maven
> > Central ...
> > > >
> > > > Any objections?
> > > >
> > > > [1] https://github.com/eclipse/californium.scandium/issues/58
> > > > [2]
> > > > https://repo.eclipse.org/content/repositories/californium-releases
> > > >
> > > > Regards,
> > > > Kai
> > > >
> > > > _______________________________________________
> > > > 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
> > > _______________________________________________
> > > 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
> > _______________________________________________
> > 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
> _______________________________________________
> 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