Hi Angus,
quite a noble intent, one that requires lots of attempts like this you
have started.
On 10/23/2014 09:32 PM, Angus Salkeld wrote:
I have felt some grumblings about usability issues with Heat
templates/client/etc..
and wanted a way that users could come and give us feedback easily
On Fri, Oct 24, 2014 at 4:00 PM, Stefano Maffulli stef...@openstack.org
wrote:
Hi Angus,
quite a noble intent, one that requires lots of attempts like this you
have started.
On 10/23/2014 09:32 PM, Angus Salkeld wrote:
I have felt some grumblings about usability issues with Heat
Angus,
There are two groups which may be relevant regarding ‘consumers’ of Heat
-Application eco system working group at
https://wiki.openstack.org/wiki/Application_Ecosystem_Working_Group
-API working group at https://wiki.openstack.org/wiki/API_Working_Group
There are some
Damn, there are multiple discussions on scheduler split while I'm on
vacation, thus I can't correctly respond the best I would...
Le 24 oct. 2014 03:11, Jay Pipes jaypi...@gmail.com a écrit :
On 10/23/2014 07:57 PM, Elzur, Uri wrote:
Today, OpenStack makes placement decision mainly based on
Hi all,
I have a question for you devs.
I don't understand the difference between this link
http://git.openstack.org/cgit/openstack/governance/tree/reference/
project-testing-interface.rst
and
https://wiki.openstack.org/wiki/ProjectTestingInterface
Some parts don't match (e.g. unittest running
Terrific idea! So what happens with the feedback you receive?
I am, of course, most interested in issues that might help us improve
the documentation, of course, but it's a general question about how
this information flows to the Product Engineering team.
meg
On Thu, Oct 23, 2014 at 11:46 PM,
Hi all,
I have a question for you devs.
I don't understand the difference between this link
http://git.openstack.org/cgit/openstack/governance/tree/reference/project-testing-interface.rst
and
https://wiki.openstack.org/wiki/ProjectTestingInterface
Some parts don't match (e.g. unittest running
Hi, Elena Ezhova, thanks for your work to this problem!
I agree with your analysis, this why I commit this bug but don't submit patch
for it.
I have want to use conntrack to solve this bug, but I also thought the
problem you have said:
The problem here is that it is sometimes
Thanks for attending meeting!
Logs:
http://eavesdrop.openstack.org/meetings/sahara/2014/sahara.2014-10-23-18.01.html
On Wed, Oct 22, 2014 at 10:33 PM, Sergey Lukjanov slukja...@mirantis.com
wrote:
Hi folks,
We'll be having the Sahara team meeting as usual in
#openstack-meeting-alt
I think the root cause of the problem here is that we are losing
segregation between tenants at the conntrack level. The compute side plugs
everything into the same namespace and we have no guarantees about
uniqueness of any other fields kept by conntrack.
Because of this loss of uniqueness, I
Hi, there are several efforts to run service in VM.[1][2][3]
Although we focused on router service, other services like lbaas have
similar requirements. So it will be good to have a BoF or something.
I created a poll page(following NFV BoF), and please register
if you're interested
Just like Kevin I was considering using conntrack zones to segregate
connections.
However, I don't know whether this would be feasible as I've never used
iptables CT target in real applications.
Segregation should probably happen at the security group level - or even at
the rule level - rather
Nice!, It sounds like a good mechanism to handle this.
Defining a good mechanism here is crucial, we must be aware of the
2^16 zones limit [1], and that ipset rules will coalesce connections
to lots of different IPs over the same rule.
May be a good option is to tag connections per rule (we
- Original Message -
Hi Miguel,
while we'd need to hear from the stable team, I think it's not such a bad
idea to make this tool available to users of pre-juno openstack releases.
As far as upstream repos are concerned, I don't know if this tool violates
the criteria for stable
While a zone per rule would be nice because we can easily delete connection
state by only referencing a zone, that's probably overkill. We only need
enough to disambiguate between overlapping IPs so we can then delete
connection state by matching standard L3/4 headers again, right?
I think a
Behazd,
Ok, for now we can do it in such way.
What I am thinking is that this *logic* should be implemented on
benchmark.runner level.
Cause different load generators are using different approaches to generate
load.
So in case of serial runner it's even impossible to make locking.
So what about
Kevin, I agree, with you, 1 zone per port should be reasonable.
The 2^16 rule limit will force us into keeping state (to tie
ports to zones across reboots), may be this state can be just
recovered by reading the iptables rules at boot, and reconstructing
the current openvswitch-agent local
sorry: when I said boot, I mean openvswitch agent restart.
- Original Message -
Kevin, I agree, with you, 1 zone per port should be reasonable.
The 2^16 rule limit will force us into keeping state (to tie
ports to zones across reboots), may be this state can be just
recovered by
Le 23/10/2014 23:55, Gabriel Hurley a écrit :
1) If you’re going to store very large amounts of data in the
session, then session cleanup is going to become an important issue to
prevent excessive data growth from old sessions.
2) SQLite is far worse to go into production with than
On Thu, 23 Oct 2014, Doug Hellmann wrote:
Thanks for the feedback Doug, it's useful.
WebTest isn’t quite what you’re talking about, but does provide a
way to talk to a WSGI app from within a test suite rather simply. Can
you expand a little on why “declarative” tests are better suited
for this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 24/10/14 11:56, Miguel Angel Ajo Pelayo wrote:
- Original Message -
Hi Miguel,
while we'd need to hear from the stable team, I think it's not
such a bad idea to make this tool available to users of pre-juno
openstack releases.
Hi all,
we are using Tempest tests to verify every changes in different OpenStack
components and we have scripts in devstack, which allow to configure
Tempest.
We want to use Tempest tests to verify different clouds, not only installed
with devstack and to do this we need to configure Tempest
Hi Timur!
https://review.openstack.org/#/c/94473/ - this is what you need:)
On Fri, Oct 24, 2014 at 2:05 PM, Timur Nurlygayanov
tnurlygaya...@mirantis.com wrote:
Hi all,
we are using Tempest tests to verify every changes in different OpenStack
components and we have scripts in devstack,
On Fri, Oct 24, 2014 at 12:27 PM, Yves-Gwenaël Bourhis
yves-gwenael.bour...@cloudwatt.com wrote:
Le 23/10/2014 23:55, Gabriel Hurley a écrit :
1) If you’re going to store very large amounts of data in the
session, then session cleanup is going to become an important issue to
prevent
All,
On my devstack setup neither image upload or image download work
for the Swift multi-tenant store in Juno (I'm getting E500s).
I'd be interested if someone can confirm.
With these changes upload/download worked for me:
glance upload
https://review.openstack.org/#/c/130757/
glance store
On 10/24/2014 01:40 PM, stuart.mcla...@hp.com wrote:
All,
On my devstack setup neither image upload or image download work
for the Swift multi-tenant store in Juno (I'm getting E500s).
I'd be interested if someone can confirm.
With these changes upload/download worked for me:
glance
On 10/24/2014 02:14 AM, Jeremy Stanley wrote:
On 2014-10-23 17:18:04 -0400 (-0400), Doug Hellmann wrote:
I think we have to actually wait for M, don’t we (K L represents
1 year where J is supported, M is the first release where J is not
supported and 2.6 can be fully dropped).
[...]
Assigning a distinct ct zone to each port sounds more scalable. This should
keep the number of zones per host contained.
What should the workflow when rules are updated or deleted be?
1) From the rule security group find ports on host where it's applied
2) kill all matching connections for those
Hello openstackers,
MagnetoDB team is proud to announce release of Juno milestone [1]
Thanks to everyone who participated and contributed!
[1] https://launchpad.net/magnetodb/juno/2014.2
--
Ilya Sviridov
isviridov @ FreeNode
___
OpenStack-dev mailing
Yes, got it. I will review this spec.
Thank you!
On Fri, Oct 24, 2014 at 3:29 PM, Andrey Kurilin akuri...@mirantis.com
wrote:
Hi Timur!
https://review.openstack.org/#/c/94473/ - this is what you need:)
On Fri, Oct 24, 2014 at 2:05 PM, Timur Nurlygayanov
tnurlygaya...@mirantis.com wrote:
Hello openstackers,
I'd like to announce my candidacy as PTL of MagnetoDB[1][2][3] project.
As a PTL of MagnetoDB I'll continue my work on building great environment
for contributors, making MagnetoDB well known and great software product.
[1] https://launchpad.net/magnetodb
[2]
Thanks for your feedback too Ihar, comments inline.
- Original Message -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 24/10/14 11:56, Miguel Angel Ajo Pelayo wrote:
- Original Message -
Hi Miguel,
while we'd need to hear from the stable team, I think it's
On 09:11 Thu 23 Oct , Flavio Percoco wrote:
According to the use-cases explained in this thread (also in the emails
from John and Mathieu) this is something that'd be good having. I'm
looking forward to seeing the driver completed.
As John mentioned in his email, we should probably sync
All,
Project Calico [1] is an open source approach to virtual networking based on L3
routing as opposed to L2 bridging. In order to accommodate this approach
within OpenStack, we've just submitted 3 blueprints that cover
- minor changes to nova to add a new VIF type [2]
- some changes to
Hi,
Mistral 0.1.1 and Mistral Client 0.1.1 have been just released. They are bugfix
releases for version 0.1.
The most important bugs fixed:
* Data Flow algorithm for direct workflows didn’t work correctly in all cases
* Workflow pretty logging was broken
* 'action_context’ parameter wasn’t
Nice work Angus ... great idea. Would love to see more of this.
-S
From: Angus Salkeld [asalk...@mirantis.com]
Sent: Friday, October 24, 2014 1:32 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [all] How can we get
On 10/23/2014 06:27 AM, Chris Dent wrote:
I've proposed a spec to Ceilometer
https://review.openstack.org/#/c/129669/
for a suite of declarative HTTP tests that would be runnable both in
gate check jobs and in local dev environments.
There's been some discussion that this may be generally
Hey y'all!
I'm taking a page from Angus and trying to pull together a list of StackTach
users. We're moving quickly on our V3 implementation and I'd like to ensure
we're addressing the problems you've faced/are facing with older versions.
For example, I know initial setup has been a concern
On 10/24/2014 03:29 PM, Mike Perez wrote:
On 09:11 Thu 23 Oct , Flavio Percoco wrote:
According to the use-cases explained in this thread (also in the emails
from John and Mathieu) this is something that'd be good having. I'm
looking forward to seeing the driver completed.
As John
Le 24/10/2014 13:30, Chmouel Boudjnah a écrit :
On Fri, Oct 24, 2014 at 12:27 PM, Yves-Gwenaël Bourhis
yves-gwenael.bour...@cloudwatt.com
mailto:yves-gwenael.bour...@cloudwatt.com wrote:
memcache can be distributed (so usable in HA) and has far better
performances then db sessions.
(I hijacked this thread to save the context but changed the subject so more
people might read it.)
Looks like we have a scheduler specific session on Thurs. at 11:00AM for 90
min. so we can use that for working out some of the specific scheduler changes
we want to do (e.g. the split for sure).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 22/10/14 12:07, Thierry Carrez wrote:
Ihar Hrachyshka wrote:
[...] For stable branches, we have so called periodic jobs that
are triggered once in a while against the current code in a
stable branch, and report to openstack-stable-maint@
On Fri, Oct 24, 2014, at 07:59 AM, Flavio Percoco wrote:
On 10/24/2014 03:29 PM, Mike Perez wrote:
On 09:11 Thu 23 Oct , Flavio Percoco wrote:
According to the use-cases explained in this thread (also in the emails
from John and Mathieu) this is something that'd be good having. I'm
Great. Thanks Dolph..
On Wed, Oct 22, 2014 at 7:20 PM, Dolph Mathews dolph.math...@gmail.com
wrote:
Great question!
For some backstory, the community interest in supporting XML has always
been lackluster, so the XML translation middleware has been on a slow road
of decline. It's a burden
Hi Elena,
On Thu, Oct 23, 2014 at 4:22 AM, Elena Ezhova eezh...@mirantis.com wrote:
Kill the connection using conntrack
The problem here is that it is sometimes impossible to tell which
connection should be killed. For example there may be two instances running
in different
Miguel Ángel,
On Thu, Oct 23, 2014 at 5:56 AM, Miguel Angel Ajo Pelayo
mangel...@redhat.com wrote:
Temporarily removing this entry doesn't seem like a good solution
to me as we can't really know how long do we need to remove this rule to
induce the connection to close at both ends (it will
Hi,
In addition to MIstral 0.1.1 bugfix release here are the first two videos from
the series of screencasts that we started this week aiming to highlight new
functionality introduced in Mistral 0.1 released in the end of Sept.
MIstral 0.1, part 1: http://www.youtube.com/watch?v=9kaac_AfNow
+100! Angus this is awesome!!! Anyway to get one of these for each
project?
Thanks,
Brad
Brad Topol, Ph.D.
IBM Distinguished Engineer
OpenStack
(919) 543-0646
Internet: bto...@us.ibm.com
Assistant: Kendra Witherspoon (919) 254-0680
From: Sandy Walsh sandy.wa...@rackspace.com
To:
On 10/23/2014 07:31 AM, Jeff Peeler wrote:
On 10/22/2014 11:04 AM, Steven Dake wrote:
A few weeks ago in IRC we discussed the criteria for joining the core
team in Kolla. I believe Daneyon has met all of these requirements by
reviewing patches along with the rest of the core team and providing
On 10/23/2014 08:57 PM, Brian Haley wrote:
On 10/23/14 6:22 AM, Elena Ezhova wrote:
Hi!
I am working on a bug ping still working once connected even after
related security group rule is
deleted (https://bugs.launchpad.net/neutron/+bug/1335375). The gist of
the problem is the following: when we
On 10/24/2014 10:39 AM, Dugger, Donald D wrote:
(I hijacked this thread to save the context but changed the subject
so more people might read it.)
Looks like we have a scheduler specific session on Thurs. at 11:00AM
for 90 min. so we can use that for working out some of the specific
scheduler
On Oct 24, 2014, at 6:58 AM, Chris Dent chd...@redhat.com wrote:
On Thu, 23 Oct 2014, Doug Hellmann wrote:
Thanks for the feedback Doug, it's useful.
WebTest isn’t quite what you’re talking about, but does provide a
way to talk to a WSGI app from within a test suite rather simply. Can
Roman Bogorodskiy wrote:
On Mon, Oct 20, 2014 at 10:19 PM, Joe Gordon joe.gord...@gmail.com wrote:
On Sat, Oct 18, 2014 at 10:04 AM, Roman Bogorodskiy
rbogorods...@mirantis.com wrote:
ping?
Roman Bogorodskiy
pgpz_SKT6P9Gy.pgp
Description: PGP signature
Thanks. I appreciate the opportunity to help the team develop Kolla. Have a
great weekend!
Regards,
Daneyon Hansen, CCIE 9950
Software Engineer
Office of the Cloud CTO
Mobile: 303-718-0400
Office: 720-875-2936
Email: daneh...@cisco.com
On Oct 24, 2014, at 8:33 AM, Steven Dake sd...@redhat.com
On 10/23/2014 11:16 PM, Angus Salkeld wrote:
Thanks for those pointers, we very interested in feedback from
operators, but
in this case I am talking more about end users not operators (people
that actually use our API).
Great! There is a working group being formed also for that.
I would
Hi,
I am trying to set up an OpenStack development workflow in our company.
We have an internal Git repository mirror of all OpenStack projects we
are working on. It is periodically updated from the upstream OpenStack
community servers. This is used to share the code among developers.
Ihar Hrachyshka wrote:
Another question to solve is how we disseminate state of those jobs.
Do we create a separate mailing list for that? Obviously we should not
reuse -dev one, and it's overkill to create one mailing list per
interest group.
Should we explore other avenues than email for
Hi Ian,
Here some details about integrating the L2-gateway (supporting multiple
plugins/MDs and not limited to OVS agent implementation) as a trunking
gateway:
It's a block, i.e. building block, that has multiple access ports as tenant
Neutron network ports (having that block type/uuid as
Hi Ondrej
The replication between Gerrit and git mirrors is done by the Gerrit
replication mechanism.
If you look at this line in the gerrit manifest:
http://git.openstack.org/cgit/openstack-infra/system-config/tree/modules/gerrit/manifests/init.pp#n255
you will see that it deploys a
The Oslo team is pleased to announce the release of stevedore version 1.1.0,
the first release in the Kilo series for stevedore.
This release includes the following fixes:
$ git log --oneline --no-merges 1.0.0..1.1.0
5749d54 Add pbr to dependency list
bb43bc4 Updated from global requirements
On 2014-10-14 11:35 AM, Adrien Cunin wrote:
Hi everyone,
Inspired by the travels tips published for the HK summit, the French
OpenStack user group wrote a similar wiki page for Paris:
https://wiki.openstack.org/wiki/Summit/Kilo/Travel_Tips
Can someone add information about pre-paid
Since I'm not going to be at summit and since I care about the
forthcoming in-tree testing stuff I was asked to write down some
thoughts prior to summit so my notions didn't get missed. Since it
is a _design_ summit after all I figured I'd take a pretty far out
position so we can go from there
+1
It would be great to know where to go in the airport and what to ask
for for a good 1 - 1.5 week prepaid GSM data plan.
Carl
On Fri, Oct 24, 2014 at 11:01 AM, Mathieu Gagné mga...@iweb.com wrote:
On 2014-10-14 11:35 AM, Adrien Cunin wrote:
Hi everyone,
Inspired by the travels tips
I also believe we can find ways to make post-merge / periodic checks useful.
We need to do that to keep the gate to a sane scale.
On 24 October 2014 17:33, Thierry Carrez thie...@openstack.org wrote:
Ihar Hrachyshka wrote:
Another question to solve is how we disseminate state of those jobs.
Do
The Oslo team is pleased to announce the release of oslo.conccurrency 0.1.0,
the first development release of the new library containing lockutils and
processutils.
Documentation for the library is available at
http://docs.openstack.org/developer/oslo.concurrency/
Please report issues via
On Fri, Oct 24, 2014 at 11:09 AM, Stefano Maffulli stef...@openstack.org
wrote:
On 10/23/2014 11:16 PM, Angus Salkeld wrote:
Thanks for those pointers, we very interested in feedback from
operators, but
in this case I am talking more about end users not operators (people
that actually
Angus Salkeld asalk...@mirantis.com wrote on 10/24/2014 12:32:04 AM:
I have felt some grumblings about usability issues with Heat
templates/client/etc..
and wanted a way that users could come and give us feedback easily
(low barrier). I started an etherpad (https://
On Fri, Oct 24, 2014 at 6:17 AM, Salvatore Orlando sorla...@nicira.com wrote:
Assigning a distinct ct zone to each port sounds more scalable. This should
keep the number of zones per host
Agree that zones could be a good solution to this problem. +1 to zone
/ port for scalability. Though it
Provider network is an extension. The API details should be at [1]
To get this to work your plugin should support the 'provider' extension.
ML2 supports it [2]. More details can be found at [3]
There is also multi-segment provider networks support. Details for that
is at [4] as mentioned by
Since I'm not going to be at summit and since I care about
notifications I was asked to write down some thoughts prior to
summit so my notions didn't get missed. The notes are at:
https://tank.peermore.com/tanks/cdent-rhat/SummitNotifications
TL;DR: make sure that adding new stuff
Hi folks,
I’d like to propose adding Malini Kamalambal (malini) as a core reviewer on the
Poppy team. She has been contributing regularly since the start of Poppy, and
has proven to be a careful reviewer with good judgment. She also brings a lot
of insight into Openstack best practices from
What scares me a bit about the “let’s find a common solution for both external
devices and VMs” approach is the challenge to reach an agreement. I remember a
rather long discussion in the dev lounge in HongKong about trunking support
that ended up going in all kinds of directions.
I work on
Thanks ... we'll be sure to address your concerns.
And there's the list we've compiled here:
https://etherpad.openstack.org/p/kilo-crossproject-summit-topics
(section 4)
-S
From: Chris Dent [chd...@redhat.com]
Sent: Friday, October 24, 2014 2:45 PM
To:
There is a formal structure via the OpenStack user committee and the associated
working groups
(https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee). We have
Monday afternoon and all of Thursday in the summit time dedicated to
discussions. The specs review process was prepared
For persistenting the graph there is also:
https://github.com/LogicalDash/gorm#gorm
The above sounds interesting...
'Object relational mapper for graphs with in-built revision control.'
It then hooks in to the https://networkx.github.io/ library which provides a
ton of useful graph
She is a very good team member, contributor and reviewer.
I vote +1!
Thanks and regards,
Obul.
From: Amit Gandhi amit.gan...@rackspace.commailto:amit.gan...@rackspace.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
-Original Message-
From: Carl Baldwin [mailto:c...@ecbaldwin.net]
Sent: 24 October 2014 19:05
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Travels tips for the Paris summit
+1
It would be great to know where to go in the airport
Okay and one other question which I must have missed; is it possible to
expand Swift capacity through Fuel? I notice Swift is installed on the
Controllers but if we need to expand Swift capacity, does that necessarily
mean Fuel requires the addition of more Controllers?
*Adam Lawson*
AQORN,
Jay-
Your faith in the ability of everyone to get concrete ideas down before the
summit is a joy to behold - I'm a little more cynical :-) I think it'll happen
in Paris.
1) Gantt specific work. Your list of BPs is great, if we can come to an
implementation plan for those on Thurs. I will be
Here are some docs highlights for this week.
HOT Guides: Gauvain wants a little more time with the HOT Guides before
making them publicly available, so those will probably come out after the
Summit.
Cutting a stable/juno branch for docs: As publicized in this week's meeting
notes, our goal is to
+1
From: Amit Gandhi [mailto:amit.gan...@rackspace.com]
Sent: Friday, October 24, 2014 2:12 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [poppy] Proposal to add Malini Kamalambal (malini) as
a Core Reviewer
Hi folks,
I'd like to propose adding
Hi,
Thanks for posting this. I am interested in this use case as well.
I didn't find a link to a review for the ML2 driver. Do you have any more
details for that available?
It seems like not providing L2 connectivity between members of the same
Neutron network conflicts with assumptions ML2 will
SQLite doesn't introduce any additional dependencies, memcached requires
installation of memcached (admittedly it's not hard on most distros, but it
*is* yet another step) and in most cases the installation of another python
module to interface with it.
Memcached might be a good choice for
With the recent talk about advanced services spinning out of Neutron,
and the fact most of the LBaaS community has wanted LBaaS to spin out of
Neutron, I wanted to bring up a possibility and gauge interest and
opinion on this possibility.
Octavia is going to (and has) an API. The current
+1 to this, eh!
Though it sounds more like you're talking about spinning the Octavia user
API out of Octavia to become it's own thing (ie. Openstack LBaaS), and
then ensuring a standardized driver interface that vendors (including
Octavia) will interface with. It's sort of a half-dozen of one,
Andrea Frittoli andrea.fritt...@gmail.com writes:
I also believe we can find ways to make post-merge / periodic checks useful.
We need to do that to keep the gate to a sane scale.
Yes, we have a plan to do that that we outlined at the infra/QA meetup
this summer and described to this list in
On Oct 24, 2014, at 3:33 AM, Angelo Matarazzo angelo.matara...@dektech.com.au
wrote:
Hi all,
I have a question for you devs.
I don't understand the difference between this link
http://git.openstack.org/cgit/openstack/governance/tree/reference/
project-testing-interface.rst
and
Hi Jorge,
I agree completely with the points you make about the logs. We still feel that
metering and logging are two different problems. The ceilometers community has
a proposal on how to meter lbaas (see
http://specs.openstack.org/openstack/ceilometer-specs/specs/juno/lbaas_metering.html)
On Oct 23, 2014, at 8:14 PM, Jeremy Stanley fu...@yuggoth.org wrote:
On 2014-10-23 17:18:04 -0400 (-0400), Doug Hellmann wrote:
I think we have to actually wait for M, don’t we (K L represents
1 year where J is supported, M is the first release where J is not
supported and 2.6 can be fully
On 10/24/2014 03:03 PM, Anne Gentle wrote:
The git link is the reference, and we're working on publishing those,
just have to get a URL/home sorted out.
In the meantime, yes, you can update the wiki page.
Why not delete the wiki altogether? I think stale content on the wiki is
damaging us
Angelo Matarazzo angelo.matara...@dektech.com.au writes:
Hi all,
I have a question for you devs.
I don't understand the difference between this link
http://git.openstack.org/cgit/openstack/governance/tree/reference/project-testing-interface.rst
and
Hi, Timur.
Check out [1]. Boris Pavlovic has been working towards what you want for more
than a full release cycle. There are still major issues to be conquered, but
having something that gets us part of the way there and can identify what can’t
be determined so that the humans have only a
The doc8 team is pleased to announce the release of doc8 0.5.0, the first
release in the kilo series for doc8.
Documentation for the library is available at http://pypi.python.org/pypi/doc8
This release includes the following changes:
$ git log 0.4.3..HEAD --oneline --no-merges
666805d Fix
93 matches
Mail list logo