[Mesa-dev] [PATCH 3/3] docs/releasing: Add note about using a staging branch

Dylan Baker dylan at pnwbakers.com
Wed May 23 16:50:32 UTC 2018

Quoting Juan A. Suarez Romero (2018-05-22 00:04:07)
> For the first two patches in the series:
> Reviewed-by: Juan A. Suarez <jasuarez at igalia.com>
> For the 3rd patch, I'm fine with the proposal, but  I would like to know the
> feedback from others. 
> In my case, for instance, I'm already using a staging branch, but in a
> completely different repository (on GitHub), as our CI integrates better here
> than with the freedesktop repository, and I have more freedom to
> add/remove/squash/reorder commits as I need in the branch.
> But as I said, I'm fine with pushing those changes also to the staging branch in
> the freedesktop repository (does it allow to force push?).

I guess I should clarify what I meant here. There should be a publicly available
branch that is updated periodically. The branch I'm using is in my mesa clone of
fdo, the real point of this is to allow others to see what's in the branch and
allow CI and QA teams the ability to test incrementally, instead of getting a
tarball and having to report "Well, that's completely broken". I added this
because I know you (Igalia) are doing this, and I've been doing this, and it's
a huge help for Mark and Clayton since they can quickly see if something is

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: signature
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180523/c90d9d02/attachment-0001.sig>

More information about the mesa-dev mailing list