On 11 October 2017 at 16:23, Gerald B. Cox <gbcox@bzb.us> wrote:

On Wed, Oct 11, 2017 at 7:23 AM, Till Hofmann <thofmann@fedoraproject.org> wrote:

The very first sentence of the page you linked above:

The updates-testing repository, also referred to as Test Updates, contains updates scheduled to be released for Branched pre-releases (after the Bodhi enabling point) and stable releases of Fedora

The point is that your update is not intended to ever make it to the stable update, i.e., it is not "scheduled to be released" for anything. If I understood correctly, you want people to test the beta version and then eventually submit the final release (i.e., not this update) to stable. I don't think that's how the updates-testing repository is supposed to be used. Instead, it should only contain updates that will eventually make it into stable.

Regards,
Till

+1 - Exactly...

Thought I'd quickly test this being built in a COPR ... but where exactly are you building from?

https://src.fedoraproject.org/rpms/firefox/blob/f27/f/firefox.spec

That shows vesion 56, not 57, and same with rawhide.

I didn't think we could build from a non-fedora-branch git branch for a bodhi update ... that feels ... wrong ...

Is this an intended effect of the "arbitrary branches" for modularity?

This really feels like it breaks the history/audit trail fro what ends up in our repos.

This doesn't even show the branch it came from: https://koji.fedoraproject.org/koji/buildinfo?buildID=981886

Surely stuff that is non-scratch in koji and intended for a Fedora compose should come from a release branch - at least outside of modularity stuff?