RFC: should we remind people to upgrade?

[Pierre-Yves David]

On 23 déc. 2012, at 21:31, Matt Mackall wrote:

> Something like 30% of bug reports are from people running copies of
> Mercurial that are a year old or more and who would benefit from
> upgrading. Perhaps we should gently remind people that their copy is
> getting stale.
> 
> Here's one way to do that:
> 
> - check the timestamp on __version__.py
> - if > 6 months, report in 'hg version' and tracebacks
> 
>        $ touch -d "dec 1 2011" mercurial/__version__.py
>        $ hg version
>        Mercurial Distributed SCM (version 2.4.1+64-1c0dfd5f1357+20121222)
>         please upgrade!
>        (see http://mercurial.selenic.com for more information)
> 
>        Copyright (C) 2005-2012 Matt Mackall and others
>        This is free software; see the source for copying conditions. There is NO
>        warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> This has the advantage of not needing any sort of 'phone home' mechanism
> nor pestering people for whom Mercurial is working just fine. If we
> deploy this in 2.5, it'll start reminding people around 2.7. Thoughts?

The overall idea is great. Maybe the message could be a bit longer

	This version is likely outdated, please upgrade!

The traceback version could even more verbose

	This version is likely outdated, please upgrade before reporting!

-- 
Pierre-Yves David