Thomas Bushnell BSG wrote: > Michael Stone writes: > > Thomas Bushnell BSG wrote: > >>Why? It's standard procedure.
Where is this documented as standard procedure? > > Only for impatient people. > > We must be talking past each other, since I'm not impatient about it > at all. 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. > What meaning do you assign to the bug report, other than the mere > documentation that a newer version has now been released upstream? Usually this implies that the maintainer is not aware of the new upstream version available. But I don't think that is the case here. Or it is a "nudge" to the maintainer if they are slow at getting a newer upstream version packaged. But that can't be the case here because it was filed so soon there has not been enough time to package and test the new one. 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. > 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? > 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. Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
