[Proposal] Rework snippet versioning

[assertchris]

Should L3 snippets be accepted?

Surely the only differentiator between snippets should be 4.0, 4.1, 4.2 etc. It would be simpler if submissions we tagged with the current version. When a new version is released all members with submissions are emailed; asking them to review and update/delete outdated snippets or face automatic deletion within 1 month.

There is a risk that content will get deleted even though it is valid. But it will ensure that all content is 1) carefully reviewed, 2) current and 3) maintained. Thoughts?

[assertchris]

Furthermore: I would be happy to spend some time reviewing these "old" snippets and conforming them to a new version. I think snippet's greatest strength is curation. I'm happy to spend time/effort for that to continue. Let's be the App Store of Laravel 4 code, not the Play Store... :)

[johnnncodes]

"Should L3 snippets be accepted?" - hmm. dunno, maybe? Any thoughts about it?

Regarding your proposal: + 💯 :)

Just make sure it doesn't really delete the snippet, just use soft deletes.