On 2016-12-13 08:29, Andreas Jaeger wrote:
> As part of the move to run master and stable/newton on Xenial, we
> disabled testing python 3.4 on these newer branches.
>
> Now, for testing we have:
> * python3.4 on older branches (stable/liberty and stable/mitaka) - on a
> trust
there's no testing currently
3) Remove python 3.4 jobs if they have no older branches (only master)
Please review your existing jobs and send changes to project-config repo,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nür
ps://etherpad.openstack.org/p/cinder-brick-driver-externals
>
> There are quite a few soft requirements under various licenses.
So, what are the steps forward here? Requiring a non-free library like
drbdmanage is not acceptable AFAIU,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twi
or is it currently flying
> under the radar ?
>
AFAIU:
http://git.openstack.org/cgit/openstack/cinder/tree/cinder/volume/drivers/drbdmanagedrv.py
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Feli
On 2016-12-12 08:34, Andreas Jaeger wrote:
> On 2016-12-12 06:20, Tony Breeds wrote:
>> On Mon, Dec 12, 2016 at 04:44:18AM +, jenk...@openstack.org wrote:
>>> Build failed.
>>>
>>> - glance-docs-ubuntu-xenial
>>> http://logs.openstack.org/38/38f
> 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
>
--
Andreas
just permissions - this is not relevant. Meetbot is in
system-config and we're at 112 channels (see common/hiera.yaml) - so not
much more space.
> Seems to indicate we have logging on 167 channels, 5-6 have full meetbot
> acess/privs
Accessbot does not setup logging,
Andreas
--
new ones but does not remove anything ? It
> should probably take its list from [1].
>
> [1]
> http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml
Is cue completely dead? Should we then retire it completely following
http://docs.openstack.org/infra/manua
On 12/01/2016 05:22 PM, Armando M. wrote:
>
>
> On 1 December 2016 at 07:45, Andreas Jaeger <mailto:a...@suse.com>> wrote:
>
> On 11/15/2016 12:30 AM, Clark Boylan wrote:
> > [...]
>
> Just a friendly reminder that this is still happenin
rks
with Xenial! Would be great if you could do this before Tuesday - you
might not be able to merge anything after the switch to Xenial,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, J
docs.o.o/developer/REPO is still for official projects only - a very old
policy that could be reevaluated by the docs team,
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, Gr
On 11/25/2016 05:26 AM, Takashi Yamamoto wrote:
> networking-midonet doesn't have stable/newton branch yet.
> newton jobs failures are false alarms.
Then let's remove these jobs,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxf
On 11/22/2016 07:56 PM, John Dickinson wrote:
>
>
> On 22 Nov 2016, at 10:47, Andreas Jaeger wrote:
>
>> When we (infra) changed the unit test jobs to not set up databases by
>> default, we created special python-db and tox-db jobs that set up both
>> MySQL and
https://review.openstack.org/400128
[9] https://review.openstack.org/400474
[10] https://review.openstack.org/394600
--
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
t content is not linked to from anywhere. You could rework
and either not publish - or only not link to the content - and only once
the new kolla-ansible content is ready, point people to it.
Choose whatever option works best for your team ;)
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org}
The above sounds like a logical differentiation.
You could have on the front-side of kolla an section "Deployment
options" that links to kolla-ansible and kolla-kubernetes.
And in kolla-ansible/kolla-kubernetes, you have a start file that links
back for generic support.
You can also s
ff in kolla, specific stuff in kolla-ansible, kolla-kubernetes?
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 fingerpr
On 2016-11-15 11:10, Paul Bourke wrote:
> Given the window for this vote is now closed and I saw no minus ones
> I'll assume this has passed. TrivialFix is now optional.
Is TrivialFix mentioned in the docs and do those need updating for the
changed policy?
Andreas
--
Andrea
?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
>
> __
> OpenStack
neral with a repo split. The
core reviewers committed to maintaining back ports properly when they voted on
the repo split.
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smi
umentation).
We're talking here about deployment guides for official OpenStack
projects - and thus OpenStack-Ansible - that are part of their repositories,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Fe
ith your request.
I expect this to be settled by Steven Dake's email:
http://lists.openstack.org/pipermail/openstack-dev/2016-October/105287.html
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Feli
On 10/28/2016 06:41 PM, Andreas Jaeger wrote:
On 10/28/2016 03:27 PM, Dave McCowan (dmccowan) wrote:
Hello Translations and Reno Team,
I'm looking for help with a the Barbican release notes job.
In the last week, our release note gate job starting failing with the
following error.
2016-
On 10/28/2016 06:41 PM, Andreas Jaeger wrote:
On 10/28/2016 03:27 PM, Dave McCowan (dmccowan) wrote:
Hello Translations and Reno Team,
I'm looking for help with a the Barbican release notes job.
In the last week, our release note gate job starting failing with the
following error.
2016-
qu...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
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 21
ean raises is how the user will figure out that they
need to use this API version and then can use the command.
Check:
http://docs.openstack.org/cli-reference/cinder.html
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürn
i-reference command from openstack-doc-tools and I
don't think we have special code in os_doc_tools/commands.py to handle
this yet.
For some commands, we run the help twice with different parameters - and
we could add for cinder the start_version for sure. I just hope it does
not remove older c
install guides being in-tree that they want to
> keep the momentum with the admin guide.
Those teams are more than welcome to contribute today to the
openstack-manuals repository! Is there anything we can help these?
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
nge get merged soonish.
thanks,
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
publish from master.
And for the api-ref - since we keep compatibility - we discussed already
earlier that publishing from the branch is not really needed or desired.
Have several documents only confuses, it's an API,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaeg
On 2016-09-29 15:10, Ruby Loo wrote:
> Hi Andreas,
>
>
>
> Because you asked so nicely, tada:
> http://docs.openstack.org/project-install-guide/baremetal/newton/
Great, thanks a lot Ruby and Ironic team!
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaege
/draft/
Be aware that this is the draft location - the version from master, so
this will soon be the Ocata version.
Once newton is released, docs.openstack.org will point to the Newton
version which is published from stable/newton branch already to:
http://docs.openstack.org/project-install-gui
On 2016-09-27 17:02, Andreas Jaeger wrote:
> On 2016-09-27 16:54, Ruby Loo wrote:
>> Hi,
>>
>>
>>
>> Thanks to the huge efforts put in by Mathieu Mitchell (mat128) and Jay
>> Faulkner (JayF), we've moved ironic's install guide from the developer
&
https://github.com/openstack/trio2o
Is there any other way to update the project description in github
repository?
github is a mirror of github and there are some API limitations, we
currently cannot update the description in github for changes.
http://git.openstack.org/cgit/openstack/tricirc
On 09/09/2016 04:34 AM, Tony Breeds wrote:
> [...]
> I did a spot check and it seems like liberty is closed for translations.
Yes, liberty is closed for translations now,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5,
On 2016-09-08 10:23, Toni Freger wrote:
> On Thu, Sep 8, 2016 at 10:52 AM, Andreas Jaeger wrote:
>>
>> This reminds me of this review for a nova-tempest-staging repository:
>> https://review.openstack.org/366091
>>
>> Joe seems to face similar challenges that yo
would
> continue to investigate ways to "unskip" these kind of tests where
> possible.
> [...]
This reminds me of this review for a nova-tempest-staging repository:
https://review.openstack.org/366091
Joe seems to face similar challenges that you articulate, John,
Andreas
--
On 2016-09-06 15:30, Ihar Hrachyshka wrote:
> Andreas Jaeger wrote:
>
>> On 2016-09-06 15:02, Ihar Hrachyshka wrote:
>>> [...]
>>> Since neutron-lib is branched on stable/* boundary, I feel that it would
>>> be fine to keep one-to-one relationship betw
On 2016-09-06 15:02, Ihar Hrachyshka wrote:
> [...]
> Since neutron-lib is branched on stable/* boundary, I feel that it would
> be fine to keep one-to-one relationship between neutron and neutron-lib
> api-ref branches.
We only publish the api-ref documents from master,
Andreas
On 09/05/2016 07:45 AM, Tony Breeds wrote:
> On Sat, Sep 03, 2016 at 07:33:42PM +0200, Andreas Jaeger wrote:
>> Reviewing all the constraints work, I see that repositories have created
>> some workaround around requirements install for one of these two legimit
>> reasons - m
On 09/03/2016 10:47 PM, Hongbin Lu wrote:
> After applying this patch [1], everything is fine. Never mind.
>
>
>
> [1] https://review.openstack.org/#/c/365126/
Please approve it quickly so that others won't run into it ;)
Andreas
--
Andreas Jaeger aj@{suse.com,o
and looks orphaned.
Instead of several projects copying and adopting these files - and thus
having them in various state in repositories - what can we do to make it
easier for developer and projects to address these two problems?
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitte
On 2016-08-28 21:57, Sean McGinnis wrote:
> On Sat, Aug 27, 2016 at 07:46:48PM +0200, Andreas Jaeger wrote:
>> On 08/26/2016 11:33 PM, Anne Gentle wrote:
>>> Hi cinder block storage peeps:
>>>
>>> I haven't heard from you on your comfort level with pu
#/c/361616 so that the cinder api-ref
follows the same patterns as other repositories - including building and
review on docs-draft.
Once those two are in, we can merge 361475.
Cinder team, could you prioritize these reviews, please?
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} T
meter, Zaqar, Senlin and Swift are
> outstanding.
>
All are merged now, check:
https://review.openstack.org/#/q/topic:os-api-ref-1.0.0-prep
We're ready for the 1.0 release of os-api-ref:
https://review.openstack.org/#/c/360038/2
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Tw
gt;
> __
> 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
>
--
And
On 08/12/2016 09:20 PM, Julien Danjou wrote:
> On Fri, Aug 12 2016, Andreas Jaeger wrote:
>
>> Projects are encouraged to create their own bindep files. Besides
>> documenting what is required, it also gives a speedup in running tests
>> since you install only what you n
m/apt
etc...
See
http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/scripts/install-distro-packages.sh
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jan
in the way of your tool, though. Is there a patch that will be
> proposed, or should I do that myself?
It's coming now ;) I didn't want to patch all 130+ repos at a time, so
did it in two steps and work on the second now,
Thanks for double checking,
Andreas
--
Andreas Jaeger aj@{sus
drivers.html#package-requirements
[2] http://docs.openstack.org/infra/bindep/
[3] https://review.openstack.org/#/q/branch:master+topic:bindep-mv
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, J
On 08/12/2016 01:44 PM, Ihar Hrachyshka wrote:
> Andreas Jaeger wrote:
>
>> On 08/12/2016 12:13 PM, Ihar Hrachyshka wrote:
>>> Jeremy Stanley wrote:
>>>
>>>> On 2016-08-11 20:19:51 +0200 (+0200), Ihar Hrachyshka wrote:
>>>>> Do I read it
gt;
> We actually publish per-release dev docs right now, though the sidebar
> seems broken:
>
> master: http://docs.openstack.org/developer/swift/
> stable release: http://docs.openstack.org/developer/swift/mitaka/
> intermediate release: http://docs.openstack.org/developer/swift/2
s unless special care is taken - like I did for translation jobs,
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
announced yesterday:
Constraints work is *now* 100 % rolled out from the infra side, it's up
to projects to use it fully now,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer
y using constraints everywhere and
showing us where it failed.
* Sachi King for making zuul-cloner usable in the post queue. This was a
missing part in the last months.
* The OpenStack infra team for many reviews and design discussions -
especially to Jeremy Stanley and Jim Blair.
--
Andreas Ja
7;s a merge conflict...
This change could be beneficial for translation sync as well,
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ürnbe
k.org/349242
Andreas
On 07/18/2016 08:09 PM, Andreas Jaeger wrote:
> While looking at coverage jobs to enable them to allow use of
> constraints in post jobs (something which has just been introduced and
> needs some more testing before we take on the other jobs), I noticed
> that we
Full documentation for the steps:
http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
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 N
'd like to be aware of
them so that I can give guidance during project-config review,
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 2
On 07/18/2016 10:03 PM, Diana Clarke wrote:
> On Mon, Jul 18, 2016 at 2:09 PM, Andreas Jaeger wrote:
>> In general, I think coverage jobs should be run as check job so
>> that you know how the coverage changes. Running them only in the post
>> job means that in practice nobo
k/turbo-hipster turbo-hipster-coverage
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
ed automatically after each merged
> commit. I have to leave Gerrit for it and it cannot be used in "gerrty"
> though, or can it?
Yes, you have to leave gerrit for it to get the link to the updated
dashboard. I'm not aware of a direct integration into gertty.
> Nevertheless,
the gate docs job aware of such json format issues?
Just move that change from docs to pep8 target,
Andreas
> References:
> [1] https://review.openstack.org/#/c/339295/1
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg,
to add/remove from everyone
> + easy to query
> - not yet available in our setup
You could also use a specific topic for these - instead of the bug/XXX,
use TOP10BUG.
Another suggestion: Check what neutron has done with their review board
that is available from http://status.openstac
there - before discussing next steps,
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
On 07/06/2016 08:27 AM, Andreas Jaeger wrote:
> On 2016-07-05 21:38, Andreas Jaeger wrote:
>> On 07/05/2016 02:52 PM, Andreas Jaeger wrote:
>>> [...]
>>> The change has merged and the python35 non-voting tests are run as part
>>> of new changes now.
>>&g
On 2016-07-05 21:38, Andreas Jaeger wrote:
> On 07/05/2016 02:52 PM, Andreas Jaeger wrote:
>> [...]
>> The change has merged and the python35 non-voting tests are run as part
>> of new changes now.
>>
>> The database setup for the python35-db variant is not workin
On 07/05/2016 02:52 PM, Andreas Jaeger wrote:
> [...]
> The change has merged and the python35 non-voting tests are run as part
> of new changes now.
>
> The database setup for the python35-db variant is not working yet, and
> needs adjustment on the infra side.
The python35-d
ted just to the default py35
> unittesting.
>
> As always let us know if you questions,
> Clark
The change has merged and the python35 non-voting tests are run as part
of new changes now.
The database setup for the python35-db variant is not working yet, and
needs adjustment on the i
s soon as you think your project is ready, you can replace py34 with
py35 for master.
>
> I tried py35 for neutron locally, and it ran without errors.
Then let it run for a day or two in our CI, discuss with neutron team,
and send a patch for project-config to change the setup,
A
eate branches, ask
somebody in that group to do it for you.
this is a general policy: We have small release teams that create
branches and tags for each project. Those are small since once you
pushed your tag/branch to gerrit, you cannot change it easily...
Andreas
--
Andreas Jaeger aj@{suse.c
king...
Btw. nothing stops the telemetry team to have a special "telemetry-docs"
repository that includes some of these guides,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix
re and how to publish.
So, I think the top-level folder is the best place for this,
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ür
-config as well - it looks odd for some projects where kilo is
removed from conditions and we still have icehouse or juno. Followup
changes are welcome.
https://review.openstack.org/334008
https://review.openstack.org/333910
https://review.openstack.org/333977
Andreas
--
Andreas Jaeger aj@{
s the docs job using
tox -e venv -- python setup.py build_sphinx
And that's where the change comes in...
So, your docs environment is not used as is in the gate,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germa
;
>
>
> __
> 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/o
ue is that the infra jobs are setup with the assumption that a
server project does not publish to pypi.
Both templates contain the same jobs and thus announcements might be
send twice.
So, if you want to publish to PyPI, remove the server-release-jobs
template...
Andreas
--
Andreas Jaeger aj@{su
https://review.openstack.org/#/c/319399/
We will not have a full from source guide - let's grow the existing one
first before adding another variation ;). The idea was AFAIR that
projects can install from source if there are no packages for them.
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.or
for someone
> to find it and get confused.
That's step 2 - see
http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
1) https://review.openstack.org/323751
2) Remove content as you suggest above
3) Make repository read-only
We need step 1 so that step 2 can merge - with the curr
http://docs.openstack.org/admin-guide/common/app_support.html
So, the reorg will not remove this page at all, no worries,
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,
d to have a repository with content and can instead start right
away - if being part of an existing project works for you,
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 Sm
UI in your browser, so it may be
> almost as easy to correct trivial issues while you're reviewing
> instead of commenting on them.
>
And that's what I'm sometimes doing if it's just some minor issues.
Edit, publish, summarize my changes - and then +2 ;). That's a reall
t;> there... I just know that others (in the oslo group) have other
>> thoughts here (and hopefully they can chime in).
>>
>> Part of this is also being refined in
>> https://review.openstack.org/#/c/312233/ and that hopefully can be a
>> guideline for new libraries tha
Looking at yourcross-project spec
https://review.openstack.org/#/c/284454/, I really wonder what's the
reason is for this developed outside of the Big Tent,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
ic to OpenStack, I wonder whether that is the right
approach. It fits nicely into Oslo as cross-project library - or it
could be an independent team on its own in the Big Tent.
But cross-project and outside of Big Tent looks very strange to me,
Andreas
[1] https://review.openstack.org/284454
--
An
p://docs.openstack.org/developer/neutron/stadium/sub_project_guidelines.html
I've just removed that page and a few others in the devref directory
that were stale - for next time, the recommendation by Matt works best...
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SU
ev/peps/pep-0503/
> [2]
> https://bitbucket.org/pypa/bandersnatch/pull-requests/20/fully-implement-pep-503-normalization/
>
> ___
> OpenStack-Infra mailing list
> openstack-in...@lists.openstack.org
> http://lists.openstack.org/cgi-bin
fra team will change the IRC topic and
update here - as response to
http://lists.openstack.org/pipermail/openstack-dev/2016-May/094588.html
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer,
On 05/10/2016 09:00 PM, Jeremy Stanley wrote:
> [...]
> Another outcome of this is that Andreas Jaeger put together some
> project-config specific reviewing guidelines:
> http://git.openstack.org/cgit/openstack-infra/project-config/plain/README.rst
> In the future, that will be exte
On 05/08/2016 01:12 AM, Nikhil Komawar wrote:
>
>
>
> On 5/7/16 4:26 PM, Andreas Jaeger wrote:
>> On 05/07/2016 10:06 PM, Nikhil Komawar wrote:
>>> Hi Andreas,
>>>
>>> Thank you for your email.
>>>
>>> I got input from a helpful sou
ack-infra if you have questions - or
provide a first change and then let's work on it together...
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,
Right now we have the Install Guide as first guide where we move content
to the teams and still want to provide this from one place.
I suggest that we do the Install Guide first and then consider whether
that is a model that we should use for other documents as well,
Andreas
--
Andreas Jaeger aj@{s
+topic:zanata/translations,n,z
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
/simpler method to do this?
That's the way to add repositories to your project,
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ür
On 05/02/2016 05:53 PM, Jeff Peeler wrote:
On Mon, May 2, 2016 at 9:50 AM, Andreas Jaeger wrote:
On 05/02/2016 03:05 PM, Steven Dake (stdake) wrote:
Swapnil,
I gather this is what people want but this cannot be done with git and
maintain history. To do this, we would have to "cp ol
On 05/02/2016 04:58 PM, Jim Rollenhagen wrote:
On Mon, May 02, 2016 at 03:52:17PM +0200, Andreas Jaeger wrote:
On 05/02/2016 03:34 PM, Jim Rollenhagen wrote:
On Thu, Apr 28, 2016 at 10:38:13AM -0500, Lana Brindley wrote:
Greetings from Austin!
Yesterday we held the Install Guide planning
work on this! :)
Let me ask this differently:
Let's assume we have one index file for the mitaka version of all
install guides which gets published at mitaka release time. Where should
we link to?
Does that help?
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegera
why choosing
two repositories up front is irreversible.
On the other hand: If you start with one and want to split later, you
can use git-filter to create a copy of the repo with just the kubernetes
files in it and set up a new repository with that content. So, you would
keep the history...
And
want to help and regenerate all tables for a project, that is
also welcome.
Keep in mind that we have no mitaka branch yet. So, our master branch
targets mitaka at the moment. Please hold back any Newton related
changes for the configuration reference,
Andreas
--
Andreas Jaeger aj@{suse.com
be fine again.
If you had a normal job falling due to UNSTABLE jobs, please issue a
"recheck". For periodic jobs like yours, let's wait for tomorrow for the
next run,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5,
201 - 300 of 502 matches
Mail list logo
