Juju is now on Github

[Horacio Duran]

Thanks for the info Ian, you guys have done a wonderful job and have been
very helpful during the day.


On Tue, Jun 3, 2014 at 8:49 PM, Ian Booth <ian.booth at canonical.com> wrote:

> Hi folks
>
> The migration of Juju source from Launchpad to Github is now complete for
> phase
> one. The final location is at https://github.com/juju/juju
>
> I say phase one because there are sill some follow up tasks to complete.
> You
> will notice that the landing process (essentially the time taken to run the
> tests) is longer. This is because we currently need to spin up an
> ephemeral EC2
> instance rather than using a nailed up instance on Canonistack. We also
> need to
> reduce the parallelism of the tests to get them reliably passing in that
> environment. Addressing these issues is high on the priority list.
>
> Note: only trunk is moved across to Github. Any work on 1.18.x will still
> need
> to be done via Launchpad.
>
> One thing you may want to do is redirect Juju project related
> notifications to a
> work email address. Folks may have previously signed up to Github accounts
> with
> personal email addresses. You can go into your profile and add a new email
> address and redirect notifications for the Juju project to prevent spam to
> your
> personal address.
>
> As a reminder, the new landing workflow is documented in the Contributing
> document https://github.com/juju/juju/blob/master/CONTRIBUTING
>
> Don't forget, if you have in progress bzr branches, these can be migrated
> across
> using the steps Martin previously sent out.
>
> <snip>
> $ cd $GOPATH/src
> $ bzr branches launchpad.net/juju-core
> * trunk
>   wip_feature
> $ bzr switch -d launchpad.net/juju-core wip_feature
> $ (cd github.com/juju/juju&&git branch)
> * master
> $ (cd github.com/juju/juju&&git checkout -b wip_feature)
> $ (cd launchpad.net/juju-core&&bzr diff -rancestor:co:trunk)|(cd
> github.com/juju/juju&&patch  -p0 --merge)
>
> Then resolve any conflicts, stage and commit.
> <snip>
>
> One improvement over the old system is that we now have visibility to how
> our
> landings are progressing. There's a link to the Jenkins landing job in the
> pull
> request email and from there you can see the console output of the test
> run.
>
> Finally, there are bound to be some rough edges and process improvements
> we can
> make as we all adjust to using this new environment. Please do speak up if
> there
> are issues that need to be addressed.
>
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140603/10002a4b/attachment.html>