builds, the ODL method of saving git bundles for
> later tagging seems like it would work fine. Are there any downsides to this
> approach?
>
> Thanks,
> Gary
>
> From: onap-tsc-boun...@lists.onap.org
> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of
anii has quit (Ping timeout: 256 seconds)
* CristinaPauna has quit (Ping timeout: 248 seconds)
tykeal @zxiiro: I'm not saying that they're producing an updated
commit, they're are literally tagging the commit that Jenkins checked out, not
one with a modified pom
Alexis
>
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 in
t;https://wiki.openstack.org/wiki/GitCommitMessages>
>
> From: on behalf of Alexis de Talhouët
>
> Date: Monday, November 27, 2017 at 12:13 PM
> To: Mike Evans via onap-discuss
> Cc: "t...@lists.onap.org"
> Subject: [onap-tsc] [Gerrit] Commit message restriction
Hi ONAP devs, committers, PTLs,
I want to start a thread wrt the commit message restriction; bellow my
observations:
- reverting a patch through gerrit UI often fails with 500 ERROR due to: commit
subject >50 characters; use shorter first paragraph
If we think about it, someone creates a patch
> On May 17, 2017, at 9:21 AM, Arul Nambi wrote:
>
> Can non TSC members vote on these kind of decisions?
>
I believe only TSC members can vote, but that doesn’t mean ONAP contributors
can’t share their thoughts.
Thanks,
Alexis___
ONAP-TSC mailing
I’m not a TSC member but I prefer Option 2
(Also, for Bell Canada, I think it should reflect Montreal, not Ottawa.)
> On May 16, 2017, at 1:23 PM, GILBERT, MAZIN E (MAZIN E)
> wrote:
>
> Team,
>
> I have two proposals for release naming. One from Rueben Klein and the other
> from Gildas Lan
