On Wed, Oct 11, 2017 at 10:24 AM, Stephen Gallagher <sgallagh(a)redhat.com>
wrote:
On Wed, Oct 11, 2017 at 1:05 PM Heiko Adams <ml(a)fedora-blog.de> wrote:
> Am Mittwoch, den 11.10.2017, 07:53 -0700 schrieb Gerald B. Cox:
>
> By definition BETA software is never intended to be pushed to stable. Fx
> 57 is BETA. When the STABLE version is released, then it can go into
> updates-testing. Not before. Again, that is the purpose of RAWHIDE.
>
> Does this mean it's also not allowed to push packaged git-snapshots of a
> software to updates-testing because they are unreleased and potentially
> unstable?
>
I think Gerald's position is overstating it. Upstream's definition of what
is "beta" or "stable" is informative but not definitive.
However, in this particular case, the maintainer has stated that this
version of the package is *not* intended to actually go to the stable
Fedora repository, which says to me that it should not be in the
updates-testing stream at all. The point of u-t is to be a last-chance
check on the quality before it goes out to all users. It's not intended to
be a prototyping location; that's one of COPR's jobs.
You need to read my entire statement in context. That is not what I
meant. As I replied to Heiko:
"My opinion however is common sense dictates that you don't put anything in
updates-testing unless you intend to push that software to stable. If you
want people to test out experimental software, put it in RAWHIDE. If it's
a git-snapshot and your INTENT is to push it to stable (for example, you're
fixing a bug) then that is OK for updates-testing.
In this instance, there is no intent to push Fx 57 BETA to stable. That's
why it does't belong in update-testing."
In this instance, I believe that RAWHIDE would be appropriate - since it
not so much a prototype as a BETA release of a single package which is
being released within a month. Something like a test release of KDE/GNOME
which is comprised of multiple packages would be ideal for COPR - but a Fx
BETA COPR would be an excellent idea also.