Hi,
Some thoughts and questions, raised in parts from past IRL discussions.
Consider it like a ping for this thread. :)
On Sun, Jan 11, 2015 at 08:07:13PM +0100, Jurre van Bergen wrote:
> Hi,
>
> For the first iteration, which is automatically build of interesting
> branches, we need to specify:
>
> * Which branches we want to build?
We might want to use several algorithms / tricks to select the branches to
be build automatically.
One of this algo could be:
0. Build all {feature,bugfix} branch that are not merged in
stable, devel and testing, and had new commits since the last release.
I have a script that does this roughly and it says that currently, that
means 11 branches. [1]
That would make sense, but might require to have some stats about how much
it has meant for the past releases. I'm not sure how to do that though.
0. We might also want a mechanism for devs to pro-actively state they want to
keep their branches being build even if the last commit was older than the
last release. IIRC
0. Do we think we might also need or want a mechanism to blacklist a branch,
or we should just assume that our algos will only select the right ones
and not hit any corner cases?
Thoughts, answers, ideas?
bert.
[1] bugfix/8680-git-without-polipo
bugfix/8714-tor-is-ready-robustness
feature/6297-save-packages-list
feature/6992-whisperback-email-address
feature/7450-openpgp-applet-exit
feature/7779-revisit-touchpad-settings
feature/8681-test-suite-ramdisk
feature/8719-mount-output-in-bug-reports
feature/jessie
feature/linux-3.18
feature/torbrowser-alpha
