653186 - (addonsdk10b5) release Add-on SDK 1.0b5

Status: RESOLVED FIXED

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

Description

[Myk Melez [:myk] [@mykmelez]]

We should release Add-on SDK 1.0b5!

Use this bug to track tasks that need to be done to release the product, like spinning candidate builds and publishing a blog post about it, as well as code blockers for the release.

To nominate a bug to block the release, comment in this bug or ask the drivers (Dave Mason or Myk Melez) about it in the discussion group, on IRC, or by email.

Comment 1

[Brian Warner [:warner :bwarner]]

bug 653210 filed about the current test failures. Potential patch (needs thought) is attached to bug 621078. I think it's a blocker.

Comment 2

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

Would bug 597837 be worth getting into b5? It's pretty low-risk, and would help people with figuring out what's wrong with their package names.

Comment 3

[Myk Melez [:myk] [@mykmelez]]

(In reply to comment #1)
> bug 653210 filed about the current test failures. Potential patch (needs
> thought) is attached to bug 621078. I think it's a blocker.

Yup, good point.  Marked as blocking (and fortunately already fixed).


(In reply to comment #2)
> Would bug 597837 be worth getting into b5? It's pretty low-risk, and would help
> people with figuring out what's wrong with their package names.

Definitely worth it.  Approved and landed.

Comment 4

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

I'm of the opinion that there should be a respin of the RC after bug 653891 gets fixed one way or the other.

Without either of those patches, there'll be lots of user-facing console spam with the "elapsed time" counters, with no real user-facing benefits from it since they're only in there to help debug the test failures.

I already brought this up with Myk on IRC earlier tonight, so this is just to keep it on the radar. :)

Comment 5

[Dietrich Ayala (:dietrich)]

+1 on comment #4. I think it's really distracting, and not generally useful enough to have it on by default.

Another blocker nomination: bug 653906. I was working on an add-on. Updated sdk source, and boom. Now I get nothing but that every time I do cfx run.

Comment 6

[Myk Melez [:myk] [@mykmelez]]

(In reply to comment #5)
> Another blocker nomination: bug 653906. I was working on an add-on. Updated sdk
> source, and boom. Now I get nothing but that every time I do cfx run.

Hmm, indeed.

Comment 7

[Brian Warner [:warner :bwarner]]

Heh, given that we released 1.0b5 on 5/5/11, I think we can close this ticket now..