On Wed, 2005-06-29 at 11:42 -0700, Jordan Ritter wrote: > Hey folks, > > Based on a new bug report this morning, I have just discovered two > very long-standing bugs (I think they've been around since early > Razor2 versions). > > Bug #1229450: Console "freeze" on unknown option > > https://sourceforge.net/tracker/index.php?func=detail&aid=1229450&group_id=3978&atid=103978 > > Bug #1229887: fork()ing for STDIN input when STDIN is a tty "hangs" shell > > https://sourceforge.net/tracker/index.php?func=detail&aid=1229887&group_id=3978&atid=103978 > > These two bugs aren't actually related. The first is a pretty > simple fix and has already been addressed in CVS, however it lead > to the discovery of the second -- since razor-* fork by default, > and, with no options, read from STDIN by default, the default case > can result in an unusable shell until the fork'd razor-agent is > killed off. See the bug for more detail. > > My question to you all is: you've never reported this before > AFAICT, so how important do you think it is to fix this now, > really? > > We just did a release, and right after doing a few others, so if > it's not that important then I'd rather raise the issue as a known > bug and let some time pass before rolling a new tarball. I'm sure > the distribution maintainers are a little annoyed by the short > successions of recent releases..
I can completely understand your concern there. But IMHO I think that any fixes which deal with matters of stabilisation (and I am inclined to include anything that fixes a "freeze" or "hang" in that class) should result in a new release. The recent issues might be a due cause of annoyance for some maintainers but really I think packaging razor is comparatively simple and that the upgrade path is not particularly problematic. These things happen from time to time, so I think it's best just to get the wrinkles ironed out and make them a thing of the past as soon as is convenient for everyone involved. Another point is that a package maintainer for a given distro is not in any way obliged to release a new version through "mainstream" channels unless they feel like it. So, even if you were to release 2.75 within the next 5 minutes, it's not as though you chaps are forcing them to keep abreast. And it shouldn't be overly demanding of their time and resources to evaluate the bugs that you mention here and decide what course of action should be taken about it, if any. Mind you, I'm merely a user and this is just my "tuppence" worth :) Regards, --Kerin Millar ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Razor-users mailing list Razor-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/razor-users
