Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

Hello, I would advice the offical OpenStack documentation about this topic: https://docs.openstack.org/infra/manual/developers.html Cédric 2017-10-19 4:23 GMT+02:00 Yujun Zhang (ZTE) : > This could do the trick but I don't quite recommend it. There would be some >

[opnfv-tech-discuss] [opnfvdocs] Online Sphinx Editor

HI Sofia, this is the online Sphinx editor I was referring to in Stockholm: https://livesphinx.herokuapp.com Best regards, Gerald === Dr. Gerald Kunzmann, Manager DOCOMO Communications Laboratories Europe GmbH Landsberger Strasse 312, 80687 Munich

Re: [opnfv-tech-discuss] [dovetail][test-wg] Feedback from Dovetail to Test WG

Hi all, A short notice reminder: In today's Test WG meeting, we will talk about the collaboration of Dovetail and the test WG and the evolution of future test areas. Please add your input and feedback to the etherpad: https://etherpad.opnfv.org/p/dovetail-testwg-feedback-collaboration Best

Re: [opnfv-tech-discuss] Support of new types in TOSCA

Hi Xiaodong and Julien, we plan to participate to the next call on zoom (on Monday 23/10). Maybe we can discuss about this new feature during the call. In the meanwhile, as Xiaodong asked, Verigraph needs a network service descriptor containing node types already available in Verigraph's

Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

On Wed, October 18, 2017 at 7:23 PM, Yujun Zhang (ZTE) wrote: > This could do the trick but I don't quite recommend it. There would be > some commits on master you do NOT want to include in stable branches. > > I suggest to pick commits carefully after inspection and do the > cherrypick one by one

Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

Hi Yujun, The stable branch is created a few weeks before the release data and a lot can happen in a few weeks. It could be lots of small commits related to docs, lots of trivial fixes. The point I wanted to make is that you do not want to see all these small detail commits on your release

Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

Cedric, This openstack document describes the normal dev workflow. The Merge section in the document is related to what Gerrit does when a patchset is +2. In this thread, we’re talking about the ability to submit a merge request to Gerrit (so this is before +2 is done). The notion of branch

[opnfv-tech-discuss] [dovetail] weekly call agenda 10/20

Hi Dovetailers Sorry for the delay in sending out this note. For this week's call, I suggest we cover: 1) We are almost mid-way through Beta, let's review a dot release for fixes/improvements, and a quick status recap. (Xudan, Eddie) 2) Any update on documentation status (Georg)

Re: [opnfv-tech-discuss] [release][euphrates] recommended list of scenarios for release in Euphrates 5.0

Hi, I just want to raise a concern the Functest team has been discussing this morning. This list is maybe good from a deployment prospective, but it seems we are lowering the bar the older OPNFV gets… I remember in the Arno and Brahmaputra days the release criteria was to pass

Re: [opnfv-tech-discuss] [release][euphrates] recommended list of scenarios for release in Euphrates 5.0

Hi Jose, Scenario owners express intent-to-release on the scenario status page . Scenario owners indicated that they wanted to release each scenario in the recommended list. I would very much like to use test results to gate release

Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

Hello Alec, Yes Functest conforms with the "classical" guidelines as we "cherry-pick" the commits from master to stable/euphrates. It results in small commits because all are small bugfixes before the release. That's the best way to easily maintain the branches. Ii could be noted that we also

Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

Again squashing is not a good technical solution as it will forbid the next cherry-picks. You will spend much more time to fix the next conflicts than cherry-picking by hand now. If you have many commits to fix docs or trivial fixes in code in the week before release, it seems that your project

[opnfv-tech-discuss] [release][euphrates] MS10 - JIRA cleanup

Team, Please click the following two JIRA filters and check whether they include any JIRA issues from your project. - Issues assigned to no release - Issues assigned to Euphrates 5.0 If you

Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

There are different approaches to handling those “cherry-picks” or “merges” from master to stable. My experience may be old fashioned, but worked very well and quite clean: - If a commit needs to be “cherry-picked” or “merged” into stable, either doc or bug fix or feature enhancement,

[opnfv-tech-discuss] Summary of Weekly Technical Community Discussion Thursday October 19

Clover<https://wiki.opnfv.org/display/PROJ/Clover>. If time permits and persons are ready, we may also continue to discuss IDF Definition and Details, and/or Feedback of Pharos 2.0. Thanks Bin [1] https://wiki.opnfv.org/display/PROJ/Tc+Minutes+20171019 [2] http://meetbot.opnfv.org/meetings/

[opnfv-tech-discuss] Weekly Technical Discussion #103

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Pacific Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT

[opnfv-tech-discuss] 答复: [availability]High Availability Project meeting on Oct. 18

Hi, all. Below are the minutes for this week’s HA project call. According to the call, I create an etherpad page for the F release planning for HA testcases. I think we can use this to collect the possible HA test cases we would like to work on for F release and future releases. @yamei &