Thanks ttx. That's the solution we need (anything not perfect would bother
someone and help others at same time, so we need solve the problem, not to
give up any side of people). I prefer to use openstack-dev mailing list for
development discussion only.

On Wed, Jun 10, 2015 at 12:33 AM Thierry Carrez <thie...@openstack.org>
wrote:

> Victor Stinner wrote:
> > Le 09/06/2015 17:50, Jordan Pittier a écrit :
> >> Hi,
> >> This has already been discussed here:
> >>
> http://lists.openstack.org/pipermail/openstack-dev/2015-March/059020.html
> >>
> >> You can always create a filter to match these emails.
> >
> > Well, I'm doing "the opposite": I want to read (all) Oslo emails, so I
> > move them into a dedicated folder in my mail box ;-)
> >
> > I like these release emails to see what changes, especially because Oslo
> > releases break things sometimes ;-) It's better to stay tuned.
>
> We are currently exploring the option to repurpose the
> openstack-announce ML to be the extensive record of release
> announcements. It's part of a larger plan to streamline library
> releases, about which Doug should start a discussion pretty soon now.
>
> If we did that, we'd likely post to openstack-announce with Reply-To set
> to openstack-dev (so that any discussion on the recent release would
> happen on the open list).
>
> --
> 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
>
__________________________________________________________________________
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

Reply via email to