Re: [onap-tsc] Release management process is broken

2018-03-01 Thread Alexis de Talhouët
On Behalf Of Alexis de Talhouët > Sent: Wednesday, February 28, 2018 11:07 AM > To: t...@lists.onap.org; onap-discuss <onap-disc...@lists.onap.org> > Subject: Re: [onap-tsc] Release management process is broken > > Does anyone has any input on the same? > > I think it

Re: [onap-tsc] Release management process is broken

2018-02-28 Thread Gary Wu
28, 2018 11:07 AM To: t...@lists.onap.org; onap-discuss <onap-disc...@lists.onap.org> Subject: Re: [onap-tsc] Release management process is broken Does anyone has any input on the same? I think it is *critical* that we can deliver tagged artifacts (whether maven, docker *and code*) fo

Re: [onap-tsc] Release management process is broken

2018-02-28 Thread Alexis de Talhouët
Does anyone has any input on the same? I think it is *critical* that we can deliver tagged artifacts (whether maven, docker *and code*) for each of our release. Most importantly, for Beijing coming in a few weeks. We had a discussion last week on the #lf-releng channel, and it seems the issue

[onap-tsc] Release management process is broken

2018-02-23 Thread Alexis de Talhouët
Hello TSC, Release management team, I just found out our release process is somewhat broken. We should never be tagging snapshot commits as releases, and tags in projects relates to SNAPSHOT. Even more, they are multiple tags pointing to the same SNAPSHOT. I can see they are released artifacts