Closed Bug 554777 Opened 16 years ago Closed 15 years ago

make cfx auto-set jetpack-core, test-harness versions to SDK version

Categories

(Add-on SDK Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: myk, Unassigned)

Details

So we don't have to update the jetpack-core and test-harness versions every time we update the SDK version (which we currently don't store anywhere but will as part of fixing this bug, f.e. in a JETPACK_SDK_VERSION environment variable), cfx should automatically set the versions of those two packages to the SDK version. This comes from bug 553718, comment 3, where Atul says, "If we want, we can omit the version from the package.json of jetpack-core and other built-in SDK packages, and modify cfx to auto-set their 'version' fields to its own version when it normalizes their data before it's used anywhere, for instance."
When we do this, we should make sure to update the release process doc <https://wiki.mozilla.org/Labs/Jetpack/Release> to reflect this change.
Target Milestone: -- → Future
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product. To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
Having done a bunch of releases since, this isn't actually a big problem. If we decide to actually do it in the future, we can always track it then.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.