RFC: Uma nova estratégia de versionamento para Discourse

This is a great change (I especially like overlapping ESRs)

Feedback:

  1. I would like to see that lifecycle graph on a centralized page so I can easily check on it, ideally with a EOL table so I can easily tell what is in and out of support at any given time and plan accordingly (at least for ESRs).

  2. Stream switching:

This would be great – but even just being able to choose which tag during setup would be huge. Or even just include the manual steps in the setup documentation. If someone wants to start on stable/ESR, it’s really not clear how to do that right now to a new administrator. (I think the answer is pass –skip-rebuild to ./launcher, then edit the version, then do rebuild for the first time, but I’m not sure.) Since otherwise the setup just immediately launches into grabbing & running the latest version, and then going backwards is asking for trouble.

(Example of the difficulty to a new admin: Right now, the #1 search result for “install discourse stable” directs to this thread, which links to another thread which explains how to upgrade to stable, but not how to install stable from scratch.)

2 curtidas