On Tue, Dec 03, 2013 at 09:40:40AM +0100, Vincent Ladeuil wrote: > > So let's use a version scheme that never produce the same version twice > so we don't have to constantly think about corner cases if we try to > reuse a version. > > Note that an alternative is to use versions inside the ci engine alone > and always create a new version when a package can go to the "golden > image". > > I realize this hasn't been thought about and I'm not proposing to switch > to that. Yet, it's something I'll keep thinking about as it will at > least split the problems around versions between internal and external > needs. > > While we have to come up with a good versioning scheme, I don't think it > falls on the PPA assigner component responsibility, it's more likely to > be part of the Branch/Source builder one.
Reading this makes me think we should perhaps provide a versioning service that will be in charge of providing a unique monotonic version for a given project/app/file/whatever. Joe -- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
