It did just occur to me there may be a slight ordering issue around making sure that NSH_SFC's release jars are published before Honeycomb publishes its release jars as some of them I believe depend on the NSH_SFC jars.

Ed

On Fri, Jan 13, 2017 at 2:55 PM, Ed Warnicke <hagbard@...> wrote:

Marek,

 

Your recollection matches mine.  Because honeycomb is using maven, it has a less complicated time of it.  So I *think* that barring unforeseen issues, you guys can do your own release mechanics as described above :)

 

Ed 

 

On Fri, Jan 13, 2017 at 1:12 AM, Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...> wrote:

Hi,

basically these are all the jars from honeycomb-merge-17.01 job.

https://jenkins.fd.io/view/honeycomb/job/honeycomb-merge-1701-ubuntu1604/3/

To release honeycomb-1.17.01 we planned to do set version for all these artifacts to 1.17.01.

Here is a change we did for 1.17.01-RC1:
https://gerrit.fd.io/r/#/c/4563/1

As a result jars in https://nexus.fd.io/content/repositories/fd.io.release/io/fd/honeycomb/
(the place we expect honeycomb release artifacts to be stored)
got updated.

As far as I remember, we followed similar steps for 16.09 release.

Is there something that I missed or some changes in 17.01 release process?

Regards,
Marek

-----Original Message-----
From: Vanessa Valderrama [mailto:vvalderrama@...]
Sent: 12 stycznia 2017 17:44
To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>
Subject: Honeycomb 17.01 Formal Release

Marek,

Can you please provide the list of artifacts for the Honeycomb 17.01 formal release?

Thank you,
Vanessa


_______________________________________________
honeycomb-dev mailing list
honeycomb-dev@...
https://lists.fd.io/mailman/listinfo/honeycomb-dev