Re: [openstack-dev] [DragonFlow][TC] State of the DragonFlow project
Excerpts from Omer Anson's message of 2018-06-04 16:53:54 +0300: > Sure. No worries. The project is still active :) > > I tagged and branched out Queens. The build failed, see the other email thread for details. Doug > > Thanks, > Omer. > > On Mon, 4 Jun 2018 at 15:25, Sean McGinnis wrote: > > > On Sun, Jun 03, 2018 at 09:10:26AM +0300, Omer Anson wrote: > > > Hi, > > > > > > If the issue is just the tagging, I'll tag the releases today/tomorrow. I > > > figured that since Dragonflow has an independent release cycle, and we > > have > > > very little manpower, regular tagging makes less sense and would save us > > a > > > little time. > > > > > > Thanks, > > > Omer > > > > > > > Thanks Omer. I part of the concern, and the thing that caught our > > attention, > > was that although the project is using the independent release model it > > still > > had stable branches created up until queens. > > > > So this was mostly a check to make sure nothing else has changed and that > > the > > project should still be considered "active". > > > > Since it has been quite a while since the last official release from the > > project, it would be good if you proposed a release to make sure nothing > > has > > broken with the release process for DragonFlow and to make all of the code > > changes since the last release available to potential consumers. > > > > Sean > > > > __ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DragonFlow][TC] State of the DragonFlow project
Sure. No worries. The project is still active :) I tagged and branched out Queens. Thanks, Omer. On Mon, 4 Jun 2018 at 15:25, Sean McGinnis wrote: > On Sun, Jun 03, 2018 at 09:10:26AM +0300, Omer Anson wrote: > > Hi, > > > > If the issue is just the tagging, I'll tag the releases today/tomorrow. I > > figured that since Dragonflow has an independent release cycle, and we > have > > very little manpower, regular tagging makes less sense and would save us > a > > little time. > > > > Thanks, > > Omer > > > > Thanks Omer. I part of the concern, and the thing that caught our > attention, > was that although the project is using the independent release model it > still > had stable branches created up until queens. > > So this was mostly a check to make sure nothing else has changed and that > the > project should still be considered "active". > > Since it has been quite a while since the last official release from the > project, it would be good if you proposed a release to make sure nothing > has > broken with the release process for DragonFlow and to make all of the code > changes since the last release available to potential consumers. > > Sean > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DragonFlow][TC] State of the DragonFlow project
On Sun, Jun 03, 2018 at 09:10:26AM +0300, Omer Anson wrote: > Hi, > > If the issue is just the tagging, I'll tag the releases today/tomorrow. I > figured that since Dragonflow has an independent release cycle, and we have > very little manpower, regular tagging makes less sense and would save us a > little time. > > Thanks, > Omer > Thanks Omer. I part of the concern, and the thing that caught our attention, was that although the project is using the independent release model it still had stable branches created up until queens. So this was mostly a check to make sure nothing else has changed and that the project should still be considered "active". Since it has been quite a while since the last official release from the project, it would be good if you proposed a release to make sure nothing has broken with the release process for DragonFlow and to make all of the code changes since the last release available to potential consumers. Sean __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DragonFlow][TC] State of the DragonFlow project
Omer Anson wrote: If the issue is just the tagging, I'll tag the releases today/tomorrow. I figured that since Dragonflow has an independent release cycle, and we have very little manpower, regular tagging makes less sense and would save us a little time. Thanks Omer! For tagging, I suggest you use a change proposed to the openstack/releases repository, so that we can test that the release will work. Don't hesitate to ping us on #openstack-releases or read the doc at: http://git.openstack.org/cgit/openstack/releases/tree/README.rst -- Thierry Carrez (ttx) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DragonFlow][TC] State of the DragonFlow project
Hi, If the issue is just the tagging, I'll tag the releases today/tomorrow. I figured that since Dragonflow has an independent release cycle, and we have very little manpower, regular tagging makes less sense and would save us a little time. Thanks, Omer On Fri, 1 Jun 2018 at 20:54, Sean McGinnis wrote: > On Fri, Jun 01, 2018 at 01:29:41PM -0400, Doug Hellmann wrote: > > That presentation says "Users should do their own tagging/release > > management" (6:31). I don't think that's really an approach we want > > to be encouraging project teams to take. > > > I hadn't had a chance to watch the presentation yet. It also states right > aroung there that there is only one dev on the project. That really > concerns > me. > > And in very strong agreement - we definitely do not want to be encouraging > project consumers to be the ones tagging and doing their own releases. > > We would certainly welcome anyone interested to get involved in the > project and > be added as an official release liaison so they can request official > releases > though. > > > I would suggest placing Dragonflow in maintenance mode, but if the > > team doesn't have the resources to participate in the normal community > > processes, maybe it should be moved out of the official project > > list instead? > > > > Do we have any sort of indication of how many deployments rely on > > Dragonflow? Does the neutron team have capacity to bring Dragonflow > > back in to their list of managed repos and help them with releases > > and other common process tasks? > > > > Excerpts from Miguel Lavalle's message of 2018-06-01 11:38:53 -0500: > > > There was an project update presentation in Vancouver: > > > > https://www.openstack.org/videos/vancouver-2018/dragonflow-project-update-2 > > > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DragonFlow][TC] State of the DragonFlow project
On Fri, Jun 01, 2018 at 01:29:41PM -0400, Doug Hellmann wrote: > That presentation says "Users should do their own tagging/release > management" (6:31). I don't think that's really an approach we want > to be encouraging project teams to take. > I hadn't had a chance to watch the presentation yet. It also states right aroung there that there is only one dev on the project. That really concerns me. And in very strong agreement - we definitely do not want to be encouraging project consumers to be the ones tagging and doing their own releases. We would certainly welcome anyone interested to get involved in the project and be added as an official release liaison so they can request official releases though. > I would suggest placing Dragonflow in maintenance mode, but if the > team doesn't have the resources to participate in the normal community > processes, maybe it should be moved out of the official project > list instead? > > Do we have any sort of indication of how many deployments rely on > Dragonflow? Does the neutron team have capacity to bring Dragonflow > back in to their list of managed repos and help them with releases > and other common process tasks? > > Excerpts from Miguel Lavalle's message of 2018-06-01 11:38:53 -0500: > > There was an project update presentation in Vancouver: > > https://www.openstack.org/videos/vancouver-2018/dragonflow-project-update-2 > > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DragonFlow][TC] State of the DragonFlow project
That presentation says "Users should do their own tagging/release management" (6:31). I don't think that's really an approach we want to be encouraging project teams to take. I would suggest placing Dragonflow in maintenance mode, but if the team doesn't have the resources to participate in the normal community processes, maybe it should be moved out of the official project list instead? Do we have any sort of indication of how many deployments rely on Dragonflow? Does the neutron team have capacity to bring Dragonflow back in to their list of managed repos and help them with releases and other common process tasks? Excerpts from Miguel Lavalle's message of 2018-06-01 11:38:53 -0500: > There was an project update presentation in Vancouver: > https://www.openstack.org/videos/vancouver-2018/dragonflow-project-update-2 > > On Fri, Jun 1, 2018 at 11:31 AM, Sean McGinnis > wrote: > > > Hello DragonFlow team, > > > > As part of reviewing release activities it was noticed that there was > > never a > > final Queens release for DragonFlow and there was never a stable/queens > > branch > > created. > > > > It appears there is still activity with this project [1], so I am > > wondering if > > we could get an update on the status of the DragonFlow. > > > > DragonFlow is under the "independent" release model, so it does not need to > > have regular cycle milestone releases [2], but we just want to make sure > > the > > project should continue under OpenStack governance and that we are not just > > missing communication on release needs. > > > > Thanks! > > Sean > > > > [1] https://github.com/openstack/dragonflow/compare/stable/pike...master > > [2] http://git.openstack.org/cgit/openstack/releases/tree/ > > deliverables/_independent/dragonflow.yaml > > > > __ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DragonFlow][TC] State of the DragonFlow project
There was an project update presentation in Vancouver: https://www.openstack.org/videos/vancouver-2018/dragonflow-project-update-2 On Fri, Jun 1, 2018 at 11:31 AM, Sean McGinnis wrote: > Hello DragonFlow team, > > As part of reviewing release activities it was noticed that there was > never a > final Queens release for DragonFlow and there was never a stable/queens > branch > created. > > It appears there is still activity with this project [1], so I am > wondering if > we could get an update on the status of the DragonFlow. > > DragonFlow is under the "independent" release model, so it does not need to > have regular cycle milestone releases [2], but we just want to make sure > the > project should continue under OpenStack governance and that we are not just > missing communication on release needs. > > Thanks! > Sean > > [1] https://github.com/openstack/dragonflow/compare/stable/pike...master > [2] http://git.openstack.org/cgit/openstack/releases/tree/ > deliverables/_independent/dragonflow.yaml > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [DragonFlow][TC] State of the DragonFlow project
Hello DragonFlow team, As part of reviewing release activities it was noticed that there was never a final Queens release for DragonFlow and there was never a stable/queens branch created. It appears there is still activity with this project [1], so I am wondering if we could get an update on the status of the DragonFlow. DragonFlow is under the "independent" release model, so it does not need to have regular cycle milestone releases [2], but we just want to make sure the project should continue under OpenStack governance and that we are not just missing communication on release needs. Thanks! Sean [1] https://github.com/openstack/dragonflow/compare/stable/pike...master [2] http://git.openstack.org/cgit/openstack/releases/tree/deliverables/_independent/dragonflow.yaml __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
