On Wed, Oct 11, 2017 at 1:37 PM Gerald B. Cox <gb...@bzb.us> wrote:
> 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. > > Actually, I'm not sure if it belongs in Rawhide either, but it's closer. The purpose of Rawhide is actually *integration*, not prototyping. Prereleases are permissible in Rawhide when it is known that this package may require coordinating other updates (such as updating to a new release of a language interpreter or a desktop environment), but in general the goal should be that Rawhide be kept reasonably stable and not treated as a free-for-all playground. In this particular case, I can see an argument here in that we probably want to have a place to work out any incompatibilities with extensions that are packaged in Fedora, but I'm not sure how many of those there are.
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
