On 2/6/19 11:54 AM, Marek Marczykowski-Górecki wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi all,
It may be a good idea to introduce regular schedule for stable [point
releases[1]. It would minimize the need to download a lot of updates
just after installation. This is even more significant, if some updates
may require non-standard update procedure (like installing new template
versions). Such releases should also be coordinated with relevant
templates maintainers.
I'm not sure what such schedule should look like, every 3 months? 6 months?
Any opinions?
[1] https://www.qubes-os.org/doc/version-scheme/#release-version.
Using a factor other than feature sets (like time) as the determinant is
a problem. The reason is that it makes it harder for tools/apps to
target Qubes according to the version number.
If you really want to do this schedule, I recommend using a sub-point
increment (just as for bug fixes) but with a date indicator also present
in all the relevant release and package files.
--
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
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 qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/8873f15b-0059-9a21-19ea-319dd230759e%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
