Pleased to announce the 0.11.0 release of git-upstream.
With source available at:
http://git.openstack.org/cgit/openstack/git-upstream
Please report any issues through launchpad:
https://bugs.launchpad.net/git-upstream
git-upstream is an open source Python application that can be
In case anyone else is looking at this:
On 16/02/16 17:43, Bailey, Darragh wrote:
> Anyone able to help out locate where the talk disappeared to as well as
> fixing my profile before the voting closes?
Jimmy McArthur has been kind enough to step in and take care of the
problem, much appre
Hi,
Submitted a talk for the upcoming summit (or at least I thought did
everything required for it to be included), however it appears to have
not appeared in the voting process. Title was "Practical Ansible hacks
used to deploy an OpenStack solution"
Looking around I've discovered that there
I've got some git aliases that handle this, so I did a quick review to
see what might be useful additions to the tool.
* Looks like passing of the branch should change the branch used for a
.gitreview file to parse
o This looks to be unnecessary with newer git-review anyway, but
Hi Kevin,
At the moment don't think I'll be able to make it, however a number of
my colleagues will be there, so definitely an opportunity.
Be happy to start the discussion here so anyone not attending can get an
idea of where things are going.
My initial thoughts are that the first 2 places
Hi,
Those present at some of the Ansible collaboration sessions at Tokyo may
recall a mention about Helion Lifecycle Manager (HLM), which constituted
a collection of ansible playbooks and particular patterns used by the
HPE Helion OS 2.0 release to deploy clouds.
We promised at the time that
I was looking at using the meetings service
(https://wiki.openstack.org/wiki/Meetings) to run and log a meeting on a
stackforge project (git-upstream -
http://git.openstack.org/cgit/stackforge/git-upstream), which seems to
focus on reoccurring meetings.
So I'm wondering how best to register an
You may find the code for pip-compile
https://github.com/nvie/pip-tools/tree/future of interest for this, as I
think they may already have a solution for the deep dependency analysis.
I've started experimenting with it for git-upstream cause GitPython have
a habbit of breaking stuff through a
On 15/01/15 23:41, Sean Dague wrote:
On 01/15/2015 06:25 PM, Joe Gordon wrote:
We can side step the dependency graphing and ordering issue by looking
at the list of curently installed packages via pip freeze and not
installing dependencies (pip install --no-deps)
After looking into this
