User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b2) Gecko/20091108 Firefox/3.6b2 Build Identifier: Over two months have been passed after the last beta release. Time to move on. And ideally, go back to periodical releases like before. Reproducible:
confirmed. also, 0.5.4 is very broken. (tinyurl command doesn't even work!). if 0.5.5pre8 is passing unit tests, should cut a release *asap*.
Status: UNCONFIRMED → NEW
Ever confirmed: true
all tests pass on trunk.
went through the active issues blocking 0.5.5, and none of them seem like they really need to block the release IMO. http://ubiquity.mozilla.com/trac/query?status=assigned&status=new&status=accepted&status=reopened&group=status&milestone=Ubiquity+0.5.5
I think this is long overdue. I've changed the bug summary to refer to 0.5.5 final, as satyr informs me that the bugfix release is all set and ready to go. I'm told that all the tests pass for Firefox 3.6 and only one test fails on trunk. Given the current state of 0.5.4 (i.e. it doesn't work on Firefox 3.6 at all), I think it's prime time to release a new version of Ubiquity, even if it is officially on hiatus. I'm told all that's needed are changes on the Labs end.
Severity: major → blocker
Summary: Release the next beta (0.5.5pre8) → Release Ubiquity 0.5.5
Cc'ing the folks who likely did the Labs end of this in the olden days.
We'll also have to make sure that the Release Notes on the wiki are up-to-date: https://wiki.mozilla.org/Labs/Ubiquity/Ubiquity_0.5.5_Release_Notes
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Summary: Release Ubiquity 0.5.5 → Release Ubiquity 0.6
You need to log in before you can comment on or make changes to this bug.