* Alfred M. Szmidt <a...@gnu.org> [2021-10-27 09:29]: > A release is a release, how it is distributed doesn't matter.
It doesn't matter if the release version is designated as such. For example, if somebody tells me to checkout stable version of Emacs, considered "release", by using specific git command, that is acceptable. But to provide to user simple access to Git repository without any designation of what is release, and what is development, is rather not responsible and brings users at risk. > In the GNU project we prefer, but do not mandate, that people put > release tar-balls on ftp.gnu.org or equivalent, it it makes sense to > not to and only provide something via Git, CVS, or what have you that > is also OK. And software shall work, not just be development version. Some software receives multiple updates per day that are not well verified or working. If Git or version control repository is given in general, without specific release branch -- this means giving to users development version, not release version. It shall be designated as such as not to cause confusion and also problems on users' computers. Take Emacs for example, development version is not release. That is because developers made clear distinction between them. Without clear designation on what is "release" each user could be downloading different version of software with different functionality. Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/