The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:
Deprecate face versions
|Affected Puppet version:||Branch:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
Versioning faces is yet another way of trying to load multiple versions of code in the same ruby runtime. The other way being environments. Since ruby does not truly support this (as Java does), we should stop pretending we support it. See #7316, #4248, #12173, #17210, #8750
When faces were created, we couldn’t install them via gems or modules. But now that we will support this in 3.0.2, we can use modules/environments or gems to manage different versions of faces, e.g. environment dev gets 0.0.2, production gets 0.0.1. I’m not sure if we just deprecate the ability to ask for a specific version, i.e. you always get the latest version, or we also deprecate versions altogether and the related code in face_collection that walks versioned directories.