There's a policy change that landed a few weeks ago (27 nov) worth looking
into:
The new policy will be as follows:
1. If the commit occurs on the default branch, then the owners of the
repository will be notified.
2. If the commit occurs on a non-default branch, the author and the
Hi all,
On Thu, 7 Mar 2013, Jacob Kaplan-Moss wrote:
On Mon, Feb 25, 2013 at 4:48 PM, Florian Apolloner
wrote:
So all in all I think we could enable travis,
I agree, +1 from me.
One issue standing in the way: Travis will try to build any branch without
a .travis.yml file as though it was
On Mon, Feb 25, 2013 at 4:48 PM, Florian Apolloner
wrote:
> So all in all I think we could enable travis,
I agree, +1 from me.
> but I have two questions:
> * How much bash magic do we want in the .travis.yml file? One option would
> be to use a separate repo like I did in my initial work:
> ht
Hi,
so during the sprints a few people (thanks to everyone involved, sadly
enough I can't remember all the names, so I refrain from mentioning an
incomplete list) worked on adding and testing travis support to Django
which resulted in this ticket: https://code.djangoproject.com/ticket/19891
an
