On 06.09.2016 17:15, Josh Berkus wrote: > On 08/22/2016 08:11 AM, Stef Walter wrote: >> So all that said, I think this is *still* something we want to do: have >> monotonously increasing version numbers. > > OK. > > There's one other technical issue: how to handle bugfixes and security > updates? > > One of the issues with "whole number" releases is that distros are > likely to include a specific version. We'll need some way for packagers > to pull in things like security updates, and the way packaging systems > -- including containers -- work, that expects some kind of major/minor > version number. > > I realize that's not how Cockpit releases work, but we need an answer > which will be acceptable to packagers.
The usual mechanism of package revisions would be in play here. For example, lets look at system in Fedora: 229 == is an upstream version 229-13 == is a downstream in Fedora 24 (bugfixes, security fixes) Or systemd in Debian: 231 == is an upstream version 231-4 == is a downstream in Debian unstable (bugfixes, etc.) Hope that makes sense. Cheers, Stef
signature.asc
Description: OpenPGP digital signature
_______________________________________________ cockpit-devel mailing list [email protected] https://lists.fedorahosted.org/admin/lists/[email protected]
