On Tue, May 20, 2014 at 8:48 PM, Ian Booth ian.bo...@canonical.com wrote:
Hi
We are looking to migrate juju-core across to github Real Soon Now™. The
timeframe is hopefully by the end of next week, but depends on how soon we can
get documentation finished, everything tested, and agreement to
On Tue, May 20, 2014 at 11:55 PM, Francesco Banconi
francesco.banc...@canonical.com wrote:
Hi all,
FYI this morning the UI team discussed about possibile paths to migrate the
store code from lp:juju-core to Github.
We are sharing this plan so that we can synchronize/collaborate with other
Hi all,
FYI this morning the UI team discussed about possibile paths to migrate the
store code from lp:juju-core to Github.
We are sharing this plan so that we can synchronize/collaborate with other
teams with similar needs in their todo list.
Here are the store package dependencies as
On Tue, 20 May 2014, David Cheney wrote:
A possible plan is as follow:
1) Migrate juju-core/thirdparty to juju/thirdparty (Github).
Since there are no dependencies here, this seems to be a good first
candidate.
nac, these are out horrors. The code we forked should either be pushed
Hi
We are looking to migrate juju-core across to github Real Soon Now™. The
timeframe is hopefully by the end of next week, but depends on how soon we can
get documentation finished, everything tested, and agreement to move ahead. It
will be the entire juju-core codebase, and from there we plan
With regard to the thirdparty package in core, I don't see that we need it any
more. The only thing in it is pbkdf2, which is available from go.crypto which
we
import from anyway for ssh authorised keys functionality. So I say we nuke it.
I'm going to fix this right now.
--
Juju-dev
