Re: Why is Fx 57 in Updates Testing?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10/11/2017 07:26 PM, Gerald B. Cox wrote:
On Wed, Oct 11, 2017 at 10:04 AM, Heiko Adams <ml@xxxxxxxxxxxxxx> 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?


As Adam mentioned apparently this isn't the "Official Policy".

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.

I think there's a bit misunderstanding here. Some parts of the FF57 update are going to be in stable as is (if the testing goes well). That includes the CSD patch [1].

The package may not be finished yet but the FF57 is almost done
and 99% of the code is going to be shipped to stable. This is not a completely different version, it may got some bugfixes but what you see is what you will almost get as stable update at Nov 14.

I'm sure the package is almost done so I don't take your argument about "completely different" package.

Due to the radical change in extension handlings and also needs to test the CSD patch [1] which I'd like to include in stable package I decided to put the FF57 to testing as early as possible. This is really a special case.

I believed that the update-testing repository is intended for testing and it's used by power users who can handle that, exclude the package from testing if needed, downgrade broken package and so on.

I'm surprised that people use updates-testing for stable/production machines, have problem with handling the update and act like newbies. If you can't handle that, don't use that. Fedora is really a bleeding edge so don't complain you get new software with new features - even as testing only :)

Also, I think your expectation about dramatic change of new extension availability for FF57 last month before the final release is false.

ma.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1283299
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux