As we start to file QA blueprints, which of these is the right place to
do them in:
https://blueprints.launchpad.net/openstack-qa or
https://blueprints.launchpad.net/tempest or is there some 3rd place we
should use?
The first one seems more generically useful, but there's a lot of old
On 11/01/2012 03:45 PM, Sean Dague wrote:
As we start to file QA blueprints, which of these is the right place to
do them in:
https://blueprints.launchpad.net/openstack-qa or
No, this is the QA documentation.
https://blueprints.launchpad.net/tempest or is there some 3rd place we
should
On 11/01/2012 04:49 PM, David Kranz wrote:
There is now a full tempest run going daily and reporting failures to
this list. But that won't work because
jenkins and gerrit cannot be launchpad members. According to the ci
folks, others have dealt with this
by moving their mailing lists to
Not a problem at all. All I need is:
- name of the list (I assume it's: openstack...@lists.openstack.org)
- one terse line to describe the list on http://lists.openstack.org
- one or more paragraphs to describe the list on its page
- email address of the administrator(s)
Cheers,
stef
On Fri 02
On 11/02/2012 11:43 AM, Stefano Maffulli wrote:
Not a problem at all. All I need is:
- name of the list (I assume it's: openstack...@lists.openstack.org)
Yes.
- one terse line to describe the list on http://lists.openstack.org
All Things QA.
- one or more paragraphs to describe the
Out of the nova live upgrade, and full gate in tempest sessions at
OpenStack Summit I think I've come up with the following blueprints that
we should be looking at over grizzly.
* tempest-testtools - remove nose from tempest and use testtools/testr
instead (this conversation mostly happened
6 matches
Mail list logo
