That's an option for the general discussion about the nag script, but unless you have a time machine handy, I don't see how you're going to change the user agent in the 1.4 builds that are now distributed all over the world. :)
Indeed; but we want to work out the long term solution as well as the short term one.
On the wider point, I think it would be a good thing to change the UA for
releases, but it does mean that someone (with suitable checkin permissions
and authorisation) needs to change the revision immediately before a
release, make a new set of builds,
Well, you change it once you branch, so there'd be no need to make a special set of builds. Or, you have cunning makefile logic which detects that we are on a branch, and changes it based on the branch name. That would be _dead_ clever.
and change it again immediately after
(before the tree is reopened).
That part isn't necessary; it would be changed on the branch, and stay that way.
Gerv
