: [openstack-dev] [trove] Adding release notes to changes
On 2016-04-17 19:04, Amrith Kumar wrote:
>> -Original Message-
>> > From: Andreas Jaeger [mailto:a...@suse.com]
>> > Sent: Sunday, April 17, 2016 4:31 AM
>> > To: OpenStack Development Mail
ack-dev@lists.openstack.org>
>> > Subject: Re: [openstack-dev] [trove] Adding release notes to changes
>> >
>> > On 04/16/2016 05:07 PM, Amrith Kumar wrote:
>>> > > Folks,
>>> > >
>>> > > We are now using reno[1] for r
> -Original Message-
> From: Andreas Jaeger [mailto:a...@suse.com]
> Sent: Sunday, April 17, 2016 4:31 AM
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [trove] Adding
On 04/16/2016 05:07 PM, Amrith Kumar wrote:
> Folks,
>
> We are now using reno[1] for release notes in trove, trove-dashboard,
> and python-troveclient.
Note that the trove-dashboard changes are not published and tested at
all, you do not have set it up in project-config yet,
Andreas
> [...]
--
. For bug numbers, it's
probably easiest just to use a format like 'Bug 1234567' to avoid this issue.
Thanks,
Peter
-Original Message-
From: Amrith Kumar [mailto:amr...@tesora.com]
Sent: April-16-16 11:07 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [trove] Adding
Folks,
We are now using reno[1] for release notes in trove, trove-dashboard,
and python-troveclient.
If you submit a change to any one of these repositories, that is going
to be visible to a user (i.e. not changes that only impact tests, or are
procedural changes relating to management of the
