Fatih mentioned that changes in F would be in a different repo after the
reorganization of the releng repo – so branching releng would technically not
be needed for Euphrates?
In any case, it does not hurt to tag (I was surprised tags were not used more
often in OPNFV repos to mark internal ver
I think it could hurt only if you select 2017.09 as tag.
I precise pbr compares version (eg 5.0) and tags then it would break
the python package.
Cédric
2017-09-11 17:20 GMT+02:00 Alec Hothan (ahothan) :
>
>
> Fatih mentioned that changes in F would be in a different repo after the
> reorganizati
Cedric,
How to tag is a completely separate discussion and I’m actually very glad that
you bring this up along with pbr ;-)
But I’m curious why you bring up the “2017.09” example as it is not a semver
tag and would not be recognized by pbr?
For example, FD.io/VPP uses year/month to tag their re
+Fatih
Alec,
The versioning format was set last spring. However, Fatih is in the
process of putting together a proposal for versioning that will take into
account changes to the release process due to the introduction of XCI. My
suggestion is that you collaborate with Fatih on that proposal.
Alec,
My comment simply highlighted a possible issue.
You can simply trigger it via Doctor by setting version = 5 in its setup.cfg
I precise doctor offers 2015.1.0 as tag.
https://git.opnfv.org/doctor/tag/?h=2015.1.0
Then you can simply call python setup.py install or pip install .
ValueError: g
Hi Cedric,
Inline…
From: Cedric OLLIVIER
Date: Monday, September 11, 2017 at 10:31 PM
To: "Alec Hothan (ahothan)"
Cc: "Beierl, Mark" , Alexandru Avadanii
, opnfv-project-leads
, "opnfv-tech-discuss@lists.opnfv.org"
, Fatih Degirmenci
Subject: Re: [opnfv-project-leads] [opnfv-tech-discuss]
Alec,
No, I'm not part of the Doctor team.
I simply fix the requirements (and then packages) over the different
OPNFV projects which are integrated inside Functest.
From Functest point of view, the requirements are key compared to the
versioning as we are currently using git (instead of pypi) to
David,
That might look obvious but perhaps you could confirm the exact branch name
moving forward (or perhaps this has not changed).
From the look of existing branches, looks like it will be
“stable/euphrates”
I assume projects can/will commit stuff on that branch until some code freeze
milesto
Hello, Alec.
The process for the euphrates.1.0, 2.0 etc is documented here:
https://wiki.opnfv.org/display/SWREL/Git+Tagging+Instructions+for+Euphrates
The stable branch essentially means that no code review can be directly
submitted against stable/euphrates. Essentially all bug fixes and chan
Hi Alec,
I really appreciate your interest in and knowledge of configuration
management and versioning. This is an important topic that doesn't get
enough attention, IMHO. I don't mind your questions at all.
Yes, you are correct about the branch name. The change in versioning has
not affected
Thanks Mark,
That is exactly what I was looking for and your explanation below makes perfect
sense (and should be added to that page).
I wonder how do we get to know when these wiki pages are created? Do I need to
attend release meetings or subscribe to some mailer?
I am relieved the tags have
Hello, Alec.
In Confluence, you can "watch" a space and will then receive email
notifications every time a page is created/updated/deleted. It's the little
[cid:A519D3C8-5EB4-4FEF-ABBA-D8F70441C283@corp.emc.com] icon for a page, or
from the home page of a space this will poop up:
[cid:D6DC9AD
David,
I have synced with Fatih already and I will do my best to help on the CD front
(time permitting).
Note that my primary involvement in OPNFV is not versioning but since my
project NFVbench is coming from a CD environment I might as well contribute
there to make sure I’m not getting into
That is, unfortunately, not correct. I copied and pasted the directions
from danube and forgot to remove the "euphrates" prefix. I will update it.
David
On Fri, Sep 15, 2017 at 12:03 PM, Beierl, Mark wrote:
> Hello, Alec.
>
> The process for the euphrates.1.0, 2.0 etc is documented here:
> ht
Thanks, Alec. As I'm sure you're aware, participation in an open source
project often involves contributing in diverse and unexpected ways. We
appreciate your interest and willingness in working with Fatih to develop a
new versioning proposal.
David
On Fri, Sep 15, 2017 at 12:43 PM, Alec Hothan
Alec,
I saw from Fatih's presentation this morning in the TSC meeting that you
are taking on the task of proposing a new versioning scheme to accommodate
XCI. Thanks for agreeing to do that. I look forward to seeing your
proposal.
David
On Fri, Sep 15, 2017 at 12:43 PM, Alec Hothan (ahothan)
16 matches
Mail list logo