Closed Bug 386918 Opened 14 years ago Closed 13 years ago

New version of JEP (0.9.6.3), please land on trunk and branch

Categories

(Plugins Graveyard :: Java (Java Embedding Plugin), defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: smichaud, Assigned: smichaud)

References

()

Details

(Keywords: verified1.8.1.8)

Attachments

(1 file, 1 obsolete file)

Attached file Change log for JEP 0.9.6.3 (obsolete) —
This version fixes a crash bug (bug 380517) that effects all branches
and (so far) has four dups.  It also (on the trunk) works around a
recent change to the nsIScriptSecurityManager interface that broke
JavaScript-to-Java LiveConnect (bug 383783).

Please land JEP 0.9.6.3 on the trunk and the 1.8 branch as soon as
conveniently possible.  I'd like to get it into Firefox 2.0.0.5.

(I assume the 1.8.0 branch is dead.  If it isn't, please land JEP
0.9.6.3 there, too.)

http://javaplugin.sourceforge.net/

Those who want to try the new version right away will need to install
it "over" the older versions currently bundled with Mozilla.org
browsers.  I recommend installing the new JEP to your
/Library/Internet Plug-Ins/ folder, then removing older copy(ies) of
the JEP from your Mozilla.org browser(s).  For more information see
the JEP Readme.
I forgot to list one of JEP 0.9.6.3's fixes.
Attachment #270979 - Attachment is obsolete: true
Blocks: 379058, 380517
Attachment #271050 - Flags: review?(joshmoz)
Comment on attachment 271050 [details]
Change log for JEP 0.9.6.3 (revised)

mento, can you have a look at this new JEP since josh is on vacation?  

Ideally, this should land on trunk sooner rather than later so it can bake and get testing coverage in order to be able to make 1.8.1.7 on the branch.
Attachment #271050 - Flags: review?(mark)
Attachment #271050 - Flags: review?(mark)
Attachment #271050 - Flags: review?(joshmoz)
Attachment #271050 - Flags: review+
Thanks, Mark!

Like Smokey, I'd like to get this landed on the trunk reasonably soon
(though I suspect that will have to wait until Josh gets back).  And
since (barring any urgent security issues) it looks like there aren't
any imminent releases on the 1.8 branch, I'd like JEP 0.9.6.3 landed
there at the same time it lands on the trunk.  This should
substantially increase its exposure to users, and the likelihood that
any remaining bugs will be shaken out before the next releases on the
branch.
I can land this on the trunk for you now if you'd like, but you'll need branch approval before it can be landed on the 1.8 branch.
Thanks!  Please do.

I think I'll wait until Josh gets back to deal with getting it landed
on the branch.
Attachment #271050 - Flags: superreview?(mikepinkerton)
Comment on attachment 271050 [details]
Change log for JEP 0.9.6.3 (revised)

rs=pink
Attachment #271050 - Flags: superreview?(mikepinkerton) → superreview+
Josh or Mark:

Please land this on the trunk as soon as you can after the tree
reopens.  It might fix (or alleviate) a trunk topcrasher (bug 390225).
Comment on attachment 271050 [details]
Change log for JEP 0.9.6.3 (revised)

JEP 0.9.6.3 might fix or alleviate a trunk topcrasher (bug 390225),
which is blocking 1.9+.  So I'm requesting approval to land this right
away.
Attachment #271050 - Flags: approval1.9?
(Following up comment #8)

The risk of landing JEP 0.9.6.3 is quite low -- I tested it thoroughly
before I released it, it contains only a few changes, and I've had
zero reports of problems since it was released a month ago.
Attachment #271050 - Flags: approval1.9? → approval1.9+
Flags: blocking1.8.1.7?
mento might get this landed this weekend (smichaud's on vacation, if I have my dates right), but adding the keyword so this doesn't get lost, whatever the story may be.
Keywords: checkin-needed
Landed on trunk.
Marking FIXED to reflect the trunk landing. Or was there more to do?
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment on attachment 271050 [details]
Change log for JEP 0.9.6.3 (revised)

> Or was there more to do?

It still needs to be landed on the branch :-)
Attachment #271050 - Flags: approval1.8.1.7?
Flags: wanted1.8.1.x+
Flags: blocking1.8.1.7? → blocking1.8.1.7+
Comment on attachment 271050 [details]
Change log for JEP 0.9.6.3 (revised)

approved for 1.8.1.7, a=dveditz for release-drivers
Attachment #271050 - Flags: approval1.8.1.7? → approval1.8.1.7+
Landed on MOZILLA_1_8_BRANCH.
verified fixed using  Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.9a8pre) Gecko/2007090404 Minefield/3.0a8pre and Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.7pre) Gecko/2007090403 BonEcho/2.0.0.7pre.
Status: RESOLVED → VERIFIED
Firefox 2.0.0.7 RC2 (dated 2007-09-15) bundles JEP 0.9.6.2.

It shouldn't -- it should bundle JEP 0.9.6.3.

Anyone know what's up?

Is RC2 (like RC1) just "a test of a new automated system for producing
release builds", which we should ignore?
I just checked, and today's 1.8 branch nightly
(2007-09-15-04-mozilla1.8) still does bundle JEP 0.9.6.3 (as have
other 1.8 branch nightlies since I landed JEP 0.9.6.3 on the 1.8
branch on 2007-08-30).
2.0.0.7 is coming off of the Gecko 1.8.1.6 relbranch and not picking up any general changes since then.
Thanks for the info, but this is a bit ... disconcerting.

Firefox 2.0.0.7 really should bundle JEP 0.9.6.3, which contains some
important fixes.

Is there a release roadmap for Firefox 2.0.0.7 somewhere online?
http://wiki.mozilla.org/Firefox doesn't have anything.
> http://wiki.mozilla.org/Firefox doesn't have anything

Now it does.

Thanks, Smokey.  (I assume you were the one who updated it.)
(From Firefox 2.0.0.7's roadmap)

> This is a security firedrill to address the issue described in bug
> 395942 ("quicktime pwns firefox")
>
> We'll take Fx 2.0.0.6 and add this one fix only.

So it's an emergency release.
Component: Java Embedding Plugin → Java (Java Embedding Plugin)
Flags: blocking1.8.1.8+
Product: Core → Plugins
Version: Trunk → unspecified
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.