Commit fd40c6d4 authored by Tails developers's avatar Tails developers
Browse files

blueprint++

parent 5d82fe3c
...@@ -18,7 +18,17 @@ The questions raised is mostly concern the _feature/*_ and _bugfix/*_ branches ...@@ -18,7 +18,17 @@ The questions raised is mostly concern the _feature/*_ and _bugfix/*_ branches
(so _topic branches_) (so _topic branches_)
Some metrics about the number of branches merged per release could give hints Some metrics about the number of branches merged per release could give hints
that might help to decide of selection process. that might help to decide of selection process. See at the bottom of this
page.
Given a branch take around 45 minutes to be build on lizard (worth case),
with two builders, lizard will be able to build something like 64 ISOs a
day.
Devs should be able to trigger automatic builds for a branch whose build
was dropped (eg. last commit too old) by pushing a dumb commit on a
timestamp file in their branch.
Proposal1: Proposal1:
...@@ -26,14 +36,6 @@ Proposal1: ...@@ -26,14 +36,6 @@ Proposal1:
* but had new commits since the previous release * but had new commits since the previous release
We should probably also let devs being able to trigger automated builds for a
branch that would not be selected by the previous algo (eg. last commit too
old).
Devs could do so that by dropping a timestamp file in their branch. The
branch would be added to the selection if this timestamp is smaller than a
certain amount of to-be-defined time.
## When to build it ## When to build it
Define the regularity we want to build topic branches, apart from being build Define the regularity we want to build topic branches, apart from being build
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment