On Sat, Apr 01, 2017 at 09:24:40AM +0200, Marek Marczykowski-Górecki wrote: > On Fri, Mar 31, 2017 at 05:00:22PM -0700, Andrew David Wong wrote: > > On 2017-03-30 17:19, Unman wrote: > > > On Wed, Mar 29, 2017 at 12:22:57AM -0700, Andrew David Wong wrote: > > >> On 2017-03-01 01:01, Andrew David Wong wrote: > > >>> Dear Qubes community, > > >>> > > >>> Qubes OS releases are normally supported for six months after each > > >>> subsequent > > >>> major or minor release (see [Supported Versions] and [Version Scheme]). > > >>> In > > >>> accordance with this policy, Qubes 3.1, which was released on > > >>> 2016-03-09, is > > >>> scheduled to reach end-of-life (EOL) on 2017-03-29 --- six months after > > >>> Qubes > > >>> 3.2 was released on 2016-09-29. We strongly urge all current Qubes 3.1 > > >>> users to > > >>> upgrade to Qubes 3.2 or newer before 2017-03-29. As always, newer > > >>> releases are > > >>> available on the [downloads] page. > > >>> > > >>> You can view this announcement on the Web at: > > >>> https://www.qubes-os.org/news/2017/03/01/qubes-os-3-1-eol-on-2017-03-29/ > > >>> > > >>> [Supported Versions]: https://www.qubes-os.org/doc/supported-versions/ > > >>> [Version Scheme]: https://www.qubes-os.org/doc/version-scheme/ > > >>> [downloads]: https://www.qubes-os.org/downloads/ > > >>> > > >> > > >> This is a reminder that Qubes 3.1 has now reached EOL as of 2017-03-29. > > >> Please upgrade to Qubes 3.2 immediately if you have not done so already. > > >> > > > > > > Should we have a concerted effort to assess remaining 3.1 bugs to either > > > close or relabel as 3.2? > > > > > > > Sounds like a good idea to me. Marek, what do you think? > > Yes, indeed. There is currently 113 such bugs open. I'd guess most of > them also affect 3.2, so IMO migrating to "3.2 updates" milestone should > be the default action. But if someone could take a look at the list and > close those related to 3.1 only, that would be great. Then, I could move > remaining ones to 3.2 in a scripted way. > > -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing?
I'm happy to take this - it would, I think, be good to see if we can build up a team of testers to run a more formal testing strategy, so I'll ask on the lists if anyone is interested in joining. Then allocate outstanding issues, and have folk work though them with reports back - I'll collate and Andrew/Marek can update the issues. (Oh no, this sounds like my day job.) If you think this sounds too formal let me know. Otherwise, I'll start tomorrow and I think we should be able to work through those in short order, at least at first triage. unman -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/20170401172903.GA27130%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
