Good Morning Alexis,
Just out of curiosity have you guys considered offering nightly builds
via PPA. I think nightly builds would be good to get testing of new
features as well as existing functionality to ensure no regressions
could have potentially been introduced.
---
Regards,
Jonathan
things rather mainstream as well so as not to increase
the entry level requirements fore new contributors?
---
Regards,
Jonathan Aquilina
Founder Eagle Eye T
On 2014-09-19
10:14, Frank Mueller wrote:
Right now I'm a bit undecided, the usage
of ReviewBoard is too fresh. But Jesse made good
Im more than willing to help improve the work flow for you guys. As well as
fixup issues you giys feel rb has
Sent from Samsung Mobile
Original message
From: Nate Finch nate.fi...@canonical.com
Date: 19/09/2014 1:32 PM (GMT+01:00)
To: Jonathan Aquilina jaquil
I am more than willing to help out wity those modifications
Sent from Samsung Mobile
Original message
From: Eric Snow eric.s...@canonical.com
Date: 19/09/2014 5:41 PM (GMT+01:00)
To: juju-dev@lists.ubuntu.com
Subject: Re: The Pros and Cons of ReviewBoard.
On Fri, Sep
Thats what im suggesting be it coding somethign from scratch or
adapting RB to make it much easier to work with.
---
Regards,
Jonathan
Aquilina
Founder Eagle Eye T
On 2014-09-19 23:01, Matthew Williams
wrote:
At the risk of opening a can of worms:
Reviewboard
doesn't have
I also suggested in another part of the thread sending an email when
a new request is submitted to all those invovled with the reviewing.
---
Regards,
Jonathan Aquilina
Founder Eagle Eye T
On 2014-09-19
23:14, Nate Finch wrote:
If we automate the creation of reviewboard
reviews whenever
If i am not mistaken if you have multiple commits in a branch git
has something built in called git squash. This obviously eliminates the
5 step process into one merge and one push.
---
Regards,
Jonathan
Aquilina
Founder Eagle Eye T
On 2014-09-16 09:44, roger peppe wrote:
On 15 September
I dont think you have to rebase though. I think you can squash
multiple commits together.
---
Regards,
Jonathan Aquilina
Founder
Eagle Eye T
On 2014-09-16 11:27, roger peppe wrote:
On 16 September
2014 09:22, Jonathan Aquilina jaquil...@eagleeyet.net wrote:
If
i am not mistaken if you
That is it indeed :)
---
Regards,
Jonathan Aquilina
Founder Eagle
Eye T
On 2014-09-16 11:58, Dimiter Naydenov wrote:
-BEGIN PGP
SIGNED MESSAGE-
Hash: SHA1
On 16.09.2014 12:32, Jonathan
Aquilina wrote:
I dont think you have to rebase though. I think
you can squash multiple
that would fit into the workflow for you guys.
---
Regards,
Jonathan Aquilina
Founder Eagle Eye T
On 2014-09-11
17:29, Matthew Williams wrote:
Hi Folks,
There seems to be a
general push in the direction of having more mocking in unit tests.
Obviously this is generally a good thing
@lists.ubuntu.com
[8] https://lists.ubuntu.com/mailman/listinfo/juju-dev
[9] mailto:david.che...@canonical.com
I know it is possible on the issue tracker to label things even pull
requests. Not sure if that would be a good way too go or not?
--
Regards,
Jonathan Aquilina
Founder Eagle Eye T
Why not use the auto update feature that is in Ubuntu. I use it and recoeve
emails about the upgrades
Sent from Samsung Mobile
Original message
From: Antonio Rosales antonio.rosa...@canonical.com
Date: 01/07/2014 21:38 (GMT+01:00)
To: Andrew Wilkins
Not trying to hijack this thread, but a suggestion for reviewing and CI
testing. I have a hunch you guys already have something in place, but
there is TRAVIS CI which integrates nicely with github repos through a
yaml file.
When a pull request is submitted it performs a build and then on the pull
In regards to this feature. Why not write a hook for github to have it
interface with LP
One of the many things I miss now that we have moved to Github/git is the
ability to put up a merge proposal with in-progress work, allowing
collaboration
on the implementation as it evolves etc.
and hosting the stuff ourselves, but it works closer to how
we
would expect.)
Gerrit might also be an option, but I'm hoping we can do pieces at a
time.
John
=:-
On Mar 14, 2014 10:33 PM, Jonathan Aquilina jaquil...@eagleeyet.net
wrote:
If you guys need help I have some experience
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
I have an interesting scenario which either is already catered for or should
be catered for.
I am currently using a local provider for testing and contribution purposes.
I bootstrapped an environment and deployed the juju-gui i then shut down the
computer and powered it on again this morning
17 matches
Mail list logo
