[EMAIL PROTECTED] (Bob Proulx) writes: > If you are not impatient for the new version then standard procedure > is to wait for the maintainer to release a new package with that newer > version. If you feel the maintainer is not aware of the new package > or is being slow at getting the new version packaged, tested and > released then filing a wishlist bug requesting it is appropriate.
I don't understand; why does a wishlist bug imply unawareness or being slow? > The filing of a wishlist bug of a new upstream version is a push to > the maintainer to get the newer version packaged and released as soon > as possible. It registers officially that a user has a need for the > new version of the program and that this need is not being met by the > present version of the package. It is useful for starting an audit > trail documenting how long it takes a maintainer to package and > release a package. It starts the clock ticking if someone is thinking > of releasing an NMU of the package. I don't think it establishes a need or anything like that. Then it would have further information saying, say, "I need this for purpose X"; if it were blocking another bug, the severity would be higher than wishlist. >> Certainly I don't open bug reports as some attempt to file a >> delinquency; the existence of a bug is not some kind of moral fault in >> the maintainer. Indeed, since this is a wishlist bug, it doesn't even >> imply that anything is wrong at all. > > Then for what purpose do you file a "new upstream available" bug? In > what way is filing this bug convergent with the upstream package > release beneficial? You mentioned this as documenting that a newer > version has been released upstream. In what way is this method of > documentation needed or useful? The BTS is there for everyone. More information is always good. So I guess the question is the other way around: what harm does it do? >> But that's just the construction I put upon it; what is the meaning >> you assign to it? > > By filing a bug, even a wishlist one, asking for a new upstream > version you are asking for the new package *now*. It implies that the > maintainer is not aware of the upstream, or is slow at getting a new > upstream packaged, or at the least not aware that users want the newer > version. No. That's just not what it means. I'm sorry you feel that way, but it sounds like you regard bug reports as implying some kind of problem. That is just not what they mean. Those extra things, if they apply, might well be mentioned in a BTS report, but in the absence of them, it's not fair of you to be bothered that you're being criticized when nobody is actually criticizing you. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
