Open Stack

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 <sean.mcginnis at gmx.com> 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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180603/c440a016/attachment.html>