WOOOT!!!
On Tue, Jun 3, 2014 at 7:38 PM, Martin Packman martin.pack...@canonical.com
wrote:
Juju development is now done on github:
https://github.com/juju/juju
See the updated CONTRIBUTING doc for the basics. To land code you want
the magic string $$merge$$ in a comment on the pull
Make it so
On Thu, Jun 5, 2014 at 6:59 AM, Menno Smits menno.sm...@canonical.com wrote:
On 5 June 2014 06:58, Jorge Niedbalski jorge.niedbal...@canonical.com
wrote:
2cents: Why not rename the CONTRIBUTING file to CONTRIBUTING.md
so it will be rendered as a markdown file by github?
That
Juju development is now done on github:
https://github.com/juju/juju
See the updated CONTRIBUTING doc for the basics. To land code you want
the magic string $$merge$$ in a comment on the pull request so the
jenkins bot picks it up.
Note that the bot is currently taking around three times
Hi all
We now have all the pieces in place to migrate juju-core to Github.
PROPOSAL: migration is scheduled to occur at 10:00 UTC Thursday 29 May.
Once the migration commences, no further landings to juju-core on Launchpad will
be possible. It is expected that juju-core will be open to accept
github.com/wallyworld/core was his test conversion, IIRC.
There is the git revision id, but yes, there is no revno.
John
=:-
On Mon, May 26, 2014 at 6:38 PM, Aaron Bentley
aaron.bent...@canonical.comwrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14-05-26 06:23 AM, Ian Booth
What can I do to help you guys out?
The main problem with TravisCI is that it doesn't actually test what you
woukd finally land if trunk gets ahead of your branch. (When you propose a
branch it merges trunk at that time and then tells you the test results.
But if you get more trunk revs, it
For code review there is gerrit
https://code.google.com/p/gerrit/
I have seen this used by the libreoffice project, and its very successful
as there can be multiple people reviewing patches which get submitted. it
integrates with any git version control and already github has a hook
available to
The main problem with TravisCI is that it doesn't actually test what you
woukd finally land if trunk gets ahead of your branch. (When you propose a
branch it merges trunk at that time and then tells you the test results.
But if you get more trunk revs, it doesn't re test.) We're used to a bot
that
