On Mon, 9 May 2016 13:08:12 -0500
Bruno Wolff III <bruno(a)wolff.to> wrote:
On Mon, May 09, 2016 at 10:59:02 -0600,
Kevin Fenzi <kevin(a)scrye.com> wrote:
>
>This model will allow us to run CI tests on Pull Requests and
>confirm that they are not going to cause syntax errors
>or other simple breakage. Additionally, this will allow us
>to properly handle changes to these repos during milestone
>Freezes (getting approval for a freeze break before pushing
>changes, etc).
Is there documentation on how to mark requests as requesting a freeze
break as opposed to ones that can wait?
Well, I guess we need to bring that up with QA, but right now the
freeze process only uses bugzilla. So you would need to file a bugzilla
bug and mention the PR or the like on it.
Are there going to be some rough guidelines for fixes that fix one
spin, but break others? For example fixes for livebase or xfce have
been known to put the games spin over size. The games spin is just a
lab, so I think it is expected to adjust, but sometimes the changes
come very late in the process and it can be hard to react in time to
make cuts to get games back under size.
Well, I was hoping to make labels for each ks, so you could watch for
bugs with the label(s) you care about. If you saw a Xfce PR that came
in and affects games, you could comment on it before it's merged.
kevin