On Fri, 1 Nov 2002, jdow wrote: >> Regardless, it is named an 'alpha' release, and as maintainer of >> the package in Red Hat Linux, it wont go into Red Hat Linux until >> it is an official stable release. If the author claims it to be >> more stable and reliable than 1.10, then he should release it as >> 1.12 or whatever and continue developing new code in a new >> development tree. >> >> It is unfortunate that this is the way it is, but it is this way >> because it has to be this way. If I were to include 1.11aX and >> then someone complain that it doesn't work for them, and then >> bitch on slashdot that Red Hat shipped a broken "alpha" version >> of cdrtools, I would not be very happy now would I? So, it wont >> happen. > >So put it into the Red Hat "alpha" directory path, rawhide. Then the >"newness" demanding bozoids can get it without it offending the other >demanding bozoids who are mortally offended by alpha code, right? Wrong. Rawhide is the codepath for internal development. The only time something like this would go into rawhide, would be if we had very very strong reason to believe that the official version would be released well within our developmental timeframe, and we personally believed that putting it in rawhide would accelerate the release, and provide useful bug reports to the upstream authors. I have no reason to believe that a new stable release of cdrtools will come out anytime before the year 2020, so until it is actually released, I plan on just bumping the release number of 1.10 and rebuilding in rawhide. People whom this isn't useable for, are free to beta test the upstream maintainer's releases and help accelerate it becoming considered "stable" by him, and hopefully also accelerate an official release. Other alternatives are freshrpms.net, rpmfind.net, freshmeat.net -- Mike A. Harris ftp://people.redhat.com/mharris OS Systems Engineer XFree86 maintainer Red Hat Inc. -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
