Author: bertagaz Date: To: The Tails public development discussion list Subject: Re: [Tails-dev] Automated builds specification
Hi,
On Sun, Mar 01, 2015 at 12:49:35PM +0100, intrigeri wrote: > bertagaz wrote (27 Feb 2015 10:07:03 GMT) :
> > Does that sound better to you?
>
> At least it does sound better to me: the problem at hand is detecting
> the transition of a branch between inactive and active state.
>
> When coming back to a branch after not having worked on it since 6+
> weeks, the first thing I do is indeed to make the branch up-to-date
> wrt. changes that happened in the last 6+ weeks, then making sure it
> still builds locally, and after that I would push the branch and it
> will become active again (from Jenkins' perspective), as
> bertagaz explained.
>
> bertagaz, DrWhax: please explain this on the blueprint -- you now
> have two proposed wordings already so it should be easy :)
