Closed Bug 566901 Opened 15 years ago Closed 15 years ago

release Jetpack SDK 0.4

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: myk, Assigned: myk)

References

()

Details

We should release Jetpack SDK 0.4. This bug tracks completion of that overall project, and its dependencies should be used to track individual tasks that need to be done for the release.
Depends on: 566904
Depends on: 566945
Depends on: 567600
Release blockers identified after rc1 have all been fixed, and I have an rc2 in hand that I'm going to wait to release until the morning. We'll want to bake the rc2 for at least two days before releasing it as 0.4 final, so that pushes back our target release date by one day, to Thursday, May 27.
I pushed an rc2 this morning, then I pushed an rc3 this afternoon after we realized that one of the fixes that was supposed to go into rc2 (bug 567642) accidentally didn't make it. The tentative release date remains the same, Thursday, May 27.
Yesterday afternoon we announced Jetpack SDK 0.4 <http://mozillalabs.com/jetpack/2010/05/27/announcing-jetpack-sdk-0-4/>! We're currently in the "feel good" stage of the release checklist <https://wiki.mozilla.org/Labs/Jetpack/SDK/0.4/Release>, which should last for at least a few days. :-) Next Tuesday we'll review the process in the regular weekly development meeting, and then we'll be done, and I'll resolve this bug.
We reviewed the process a couple weeks ago, I just forgot to close this bug afterwards. Rectifying.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
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
You need to log in before you can comment on or make changes to this bug.