Just my two bits. As a user, I would like to have a "tagged release", similar to how I run ubuntu LTS server for years before upgrading.
I run msys2 behind a firewall, so the security updates seem not important. If my firewall is penetrated, everything on my computer would be affected. I'm looking for a "stable, reproducible work environment". I would probably not use "rolling releases". Of course, it would depend on the size of the distributions, but for most people, I believe saving disk space is no longer a big concern. I have not run into any of the incompatibilities or problems that at least a few people seem to have reported. Perhaps that is because I have not updated anything for several years? Daniel On 2/24/2017 3:13 AM, Mario Emmenlauer wrote: > > Dear Matthew Postiff and Daniel Goldman, > > This is actually a valuable input that I did not consider before! This > would enable you to ensure a fixed environment as required i.e. for build > and test systems, or for a shared work environment. While I can see good > arguments for rolling releases (security updates etc), I can also see > good benefit in tagged releases (stable, reproducible work environment). > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Msys2-users mailing list Msys2-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/msys2-users
