Bug 87851 (xchat2)
Summary: | This is the version police | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Trever Adams <trever> |
Component: | xchat | Assignee: | Mike A. Harris <mharris> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-05-29 23:40:56 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Trever Adams
2003-04-03 05:31:25 UTC
>I noticed in Phoebe and Rawhide that xchat is still 1.8.11. This doesn't seem >right as Xchat 2.0 seems to have all features of 1.8.11 and is more up to date >for the destkop. During Red Hat Linux 9 development, xchat 2.x was *NOT* available until *long* after our code freeze. Red Hat does not throw in brand new random software versions 10 minutes before we go gold. The purpose of releasing beta tests of the distribution, is to have software tested and get feedback and bug reports, and fix as many problems as possible before the next beta release, and the next, and before the final gold release. If you cram new software versions into the distribution up until the final day, then you get zero beta testing, since you are throwing away the beta testing that was done on that software when you replace it with a major new version. >I am sure there might be reason with some software to not >include updated versions You are correct, and xchat is not an exception. >however, Xchat does seem to be stable and does seem to >have released 2.0 (in february) in time for release in RH9 Wrong. It was not released anywhere near the time it would have had to be released in order to get into Red Hat Linux 9. During the creation of Red Hat Linux there are specific dates that freezes occur on, and once a certain date has occured, certain software versions are locked in stone. As time goes on, other software is locked in stone. The software must get public beta testing, and as such, some software *must* get into the distribution *before* the first public beta. Other software before the second beta, and other software before the third beta. In order to consider updating any piece of software, it must also meet a number of other criterion, both Red Hat policies, as well as developer discretions. xchat 2.0 was not released in time to be even remotely considered for inclusion. As the xchat maintainer here, and an xchat user whom has it running 24/7, I can assure you that xchat 2.x will be included in the distribution at a future time. That may be as an enhancement, or it might wait until the next distribution release depending on many factors. There is no need for me to track this in bugzilla, as it will "just happen" when I feel the time is right. Proper quality assurance matters more to me than flashy version number changes with zero testing. Watch Red Hat rawhide if you want to know when it gets first included in the distro. I don't expect it will be long. It definitely wont be enhancement erratum anytime soon though. Closing NOTABUG. *** Bug 88427 has been marked as a duplicate of this bug. *** xchat 2.0.2 has been in rawhide for a while now. |