xstatic packages would benefit highly from a 4th component or something similar.
Registered by
Matthew D. Wood
Horizon currently uses xstatic to package javascript libraries in a manner
that is apparently acceptable to the distros and also works for everyone else.
When we grab a javascript library (Jasmine 2.2.0 for example) we'd really like
to have the xstatic-package's version represent the wrapped package's version.
So jasmine-2.2.0 -> xstatic-
and if we need to make a change it would go to xstatic-
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Matthew D. Wood
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
4th component is not needed, if JS upstream is following semver.
PBR should just be smart enough to parse first 2 as MAJOR.MINOR and PATCH should be the rest, with dot included
e.g. xstatic-
(?)
