Re: [openstack-dev] [trove] Adding release notes to changes

2016-04-18 Thread Peter Stachowski 
Right, we are still waiting on the final +2/+1 for that  ;)

See https://review.openstack.org/#/c/306018/

Thanks!
Peter

-Original Message-
From: Andreas Jaeger [mailto:a...@suse.com] 
Sent: April-18-16 2:32 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [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 Mailing List (not for usage questions) 
>> > <openstack-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 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,
> [amrith] Oink? I thought this was dealt with in 
> https://review.openstack.org/#/c/306012/
> 
> Yes, there are currently no release notes for trove-dashboard, and I know 
> that the release notes jobs need to be added in zuul etc., Am I missing 
> something else?
> 

That's all I wanted to point out - add it to project-config repo.
Without that, you have no job to test and publish the release notes,

Andreas
--
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126


__
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] [trove] Adding release notes to changes

2016-04-18 Thread Andreas Jaeger 
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 Mailing List (not for usage questions)
>> > <openstack-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 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,
> [amrith] Oink? I thought this was dealt with in 
> https://review.openstack.org/#/c/306012/
> 
> Yes, there are currently no release notes for trove-dashboard, and I know 
> that the release notes jobs need to be added in zuul etc., Am I missing 
> something else?
> 

That's all I wanted to point out - add it to project-config repo.
Without that, you have no job to test and publish the release notes,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126


__
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] [trove] Adding release notes to changes

2016-04-17 Thread Amrith Kumar 
> -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 release notes to changes
> 
> 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,

[amrith] Oink? I thought this was dealt with in 
https://review.openstack.org/#/c/306012/

Yes, there are currently no release notes for trove-dashboard, and I know that 
the release notes jobs need to be added in zuul etc., Am I missing something 
else?

> 
> Andreas
> > [...]
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>GF: Felix Imendörffer, Jane Smithard, Graham Norton,
>HRB 21284 (AG Nürnberg)
> GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
> 
> 
> __
> 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] [trove] Adding release notes to changes

2016-04-17 Thread Andreas Jaeger 
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
> [...]
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
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] [trove] Adding release notes to changes

2016-04-16 Thread Peter Stachowski 
Just a note that certain character combinations cannot be used in the yaml file 
text as they are parsed (such as ': ' and '- ' that is a colon or dash with a 
space after). If you need to use either a colon or dash, then you cannot have a 
space, or you must enclosed the entire text in quotes. 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 release notes to changes

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 repository etc.,) please DO add a release 
note.

For instructions on how to add a release note, please see [2].

Once you add a release note, please be sure to run

tox -e releasenotes 

before you push your change set for review. It will save you a lot of time, and 
will spare the CI a lot of unnecessary testing.

If you are fixing a bug, please include the LP bug number(s) in the release 
note.

Some samples of release notes are provided in [3], [4], and [5].

Thanks,

-amrith

[1] http://docs.openstack.org/developer/reno/
[2]
http://docs.openstack.org/project-team-guide/release-management.html#how-to-add-new-release-notes
[3]
https://review.openstack.org/#/c/237184/6/releasenotes/notes/fix-cluster-issues-2651eaf31a85b11f.yaml
[4]
https://review.openstack.org/#/c/39/4/releasenotes/notes/fix-mysql-replication-bf2b131994a5a772.yaml
[5]
https://review.openstack.org/#/c/301936/4/releasenotes/notes/locality-support-for-clusters-78bb74145d867df2.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-dev] [trove] Adding release notes to changes

2016-04-16 Thread Amrith Kumar 
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 repository etc.,)
please DO add a release note.

For instructions on how to add a release note, please see [2].

Once you add a release note, please be sure to run

tox -e releasenotes 

before you push your change set for review. It will save you a lot of
time, and will spare the CI a lot of unnecessary testing.

If you are fixing a bug, please include the LP bug number(s) in the
release note.

Some samples of release notes are provided in [3], [4], and [5].

Thanks,

-amrith

[1] http://docs.openstack.org/developer/reno/
[2]
http://docs.openstack.org/project-team-guide/release-management.html#how-to-add-new-release-notes
[3]
https://review.openstack.org/#/c/237184/6/releasenotes/notes/fix-cluster-issues-2651eaf31a85b11f.yaml
[4]
https://review.openstack.org/#/c/39/4/releasenotes/notes/fix-mysql-replication-bf2b131994a5a772.yaml
[5]
https://review.openstack.org/#/c/301936/4/releasenotes/notes/locality-support-for-clusters-78bb74145d867df2.yaml



signature.asc
Description: This is a digitally signed message part
__
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