[RFC] Shall deprecated modules be treated specially?

[andrekeller]

When a puppet module on puppetforge is deprecated, the maintainer does so by setting version 999.999.999. crmngr will happily update to this version (i.e. when updating to latest availabel version).

This seems a bit counter-intuitive. How should we go forward here?

1. Keep the current behaviour -> no special treatment
2. Let the user specify 999.999.999 as version, but issue a warning
3. Pick the second to last version and issue a warning that the module is deprecated, manually specifying 999.999.999 is not possible
4. Just pick the second to last version without warning, manually specifying 999.999.999 is not possible.

I personally think option 3 is the most intuitive variant. Any opinions @tobru ?

[tobru]

Go for 3!

[vanElden]

I vote 2.