boun...@lists.opnfv.org] On Behalf Of Alec Hothan
(ahothan)
Sent: Wednesday, September 27, 2017 3:26 PM
To: Alexandru Avadanii ;
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed
Thanks for bringing up the multi-arch support and yes if we decide to go
han)
Sent: Wednesday, September 27, 2017 11:01 PM
To: Jose Lausuch; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed
Jose,
I am fine with using the “release-” prefix instead. Any prefix can work. If we
want something shorter: rel-5.0.
PM
To: Jose Lausuch; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed
Jose,
I am fine with using the “release-” prefix instead. Any prefix can work. If we
want something shorter: rel-5.0.0. We can leave that decision to David.
Note that
: Jose Lausuch
Date: Wednesday, September 27, 2017 at 12:17 PM
To: "Alec Hothan (ahothan)" ,
"opnfv-tech-discuss@lists.opnfv.org"
Cc: "MORTON, ALFRED C (AL)" , Raymond Paik
Subject: Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed
+1
What about usi
ailto:opnfv-tech-discuss-boun...@lists.opnfv.org
> <mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>] On Behalf Of Frank
> Brockners (fbrockne)
> Sent: Tuesday, September 26, 2017 4:44 AM
> To: Alec Hothan (ahothan); opnfv-tech-discuss@lists.opnfv.org
> <mailto:opnfv-tec
rg
> *Subject:* Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed
>
>
>
> +1 – per what Alec mentioned below, the new tagging scheme is only a small
> change incremental change from the earlier plans, but offers a lot of
> flexibility moving forward.
>
>
: Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed
+1 – per what Alec mentioned below, the new tagging scheme is only a small
change incremental change from the earlier plans, but offers a lot of
flexibility moving forward.
Frank
From: Alec Hothan (ahothan)
Sent: Montag, 25
McBride ; Fatih Degirmenci
; Frank Brockners (fbrockne)
; Tallgren, Tapio (Nokia - FI/Espoo)
Subject: [opnfv-tech-discuss] urgent euphrates git tags vote needed
I would like to get a quick vote from any person that works directly or
indirectly with code in OPNFV
Please reply with -1, 0 +1
+1
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Georg Kunz
Sent: 2017年9月26日 15:37
To: Alec Hothan (ahothan) ;
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed
+1
From
+1
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alec Hothan
(ahothan)
Sent: Monday, September 25, 2017 9:34 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] urgent euphrates git tags vote needed
I
Yujun Zhang (ZTE)"
Date: Monday, September 25, 2017 at 5:55 PM
To: "Alec Hothan (ahothan)" ,
"opnfv-tech-discuss@lists.opnfv.org"
Subject: Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed
I had a quick look at the wiki page and try to understand the rat
I had a quick look at the wiki page and try to understand the rationale
behind proposal.
If I understand it correctly, it is like
- *opnfv-x.y.z* to sync with OPNFV official releasing cycle, i.e. Danube,
Euphrates (opnfv-5.y.z).
- *(optional) x.y.z* for project intermediate release which is manag
I plan to devote a large portion of the release meeting to this topic
tomorrow. Please come prepared with your questions for Alec. I think that
this change puts us on the path which will eventually lead toward a
consolidated release process that incorporates the quickly evolving XCI
system. I wo
I would like to get a quick vote from any person that works directly or
indirectly with code in OPNFV
Please reply with -1, 0 +1
For using prefixed git tags for the Euphrates release: “opnfv-5.0.0”
This is a slight change to the plan on record (which was to use “5.0.0”). This
does NOT impact
14 matches
Mail list logo
