Re: [Tails-dev] Automated builds specification

Delete this message

Reply to this message
Autor: intrigeri
Data:  
A: The Tails public development discussion list
Assumpte: Re: [Tails-dev] Automated builds specification
Hi,

bertagaz wrote (29 Mar 2015 13:04:11 GMT) :
> On Wed, Mar 25, 2015 at 04:44:32PM +0100, intrigeri wrote:
>> => bertagaz and Jurre, may you please capture this problem, and the
>> long-term solution ideas we had, in the "Future ideas" section of
>> the blueprint?


> Done in scenarios 14 and 15, please review.


Scenario 15 looks good.

I don't understand what scenario 14 is about, especially right after
the discussion we've had on this thread. How could base branches be
possibly affected by changes in topic branches?

  * by a commit to the Git topic branch: that's not the case unless
    one then merges the topic branch into the base one, but then this
    adds new commits to the topic branch, and is already dealt with by
    other scenarios


  * by a package upload: as said earlier in this thread, one MUST NOT
    upload new packages to a topic branch's APT suite once it has been
    merged, so this should not happen (instead, I think we need
    "something" to let us remember we should simply forbid such
    dangerous actions with technical means)


Did I miss anything, or were you a little bit confused?

Cheers,
--
intrigeri