Closed Bug 1555 Opened 26 years ago Closed 26 years ago

ss: Gecko Developer Preview has prematurely time bombed itself

Categories

(Core Graveyard :: Viewer App, defect, P1)

Product:
Core Graveyard
Component:
Viewer App
Platform:
x86
Windows 95
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: Chris.Yeh, Assigned: angus)

Details

Turn on the timebombs so that the technology demonstration viewer app expires.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
timebomb activated. Warning time is January 10th, 1999, at 00:01 am.
Expire time is February 1st, 1999 at 00:01 am.

No dialogs come up. All timebomb warning and expire information is spewed to the
console.
Summary: SS: Turn on timebombs for technology demonstration. → ss:Turn on timebombs for technology demonstration.
Changing SS: to ss: in Summary so that this bug shows up properly on queries to
be Verified.
cyeh, can you confirm that this is workink ok for 11/24 build and ark Verified
please?  should be in both viewer and xpviewer apps.
i could, but that violates the basic QA premise that the person who made the fix
shouldn't be testing it.

testing this is really easy. just take your system clock, bump it to February
2nd of 1999, and then try and browser to URL's. It shouldn't let you.

I'm packing to leave on vacation at this exact moment, so I can't test it
anyway.
Status: RESOLVED → VERIFIED
Verified fixed (NT 4 SP 4 only).
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Summary: ss:Turn on timebombs for technology demonstration. → ss: Gecko Developer Preview has prematurely time bombed itself
Reopening bug so we can track this. Adding people to cc: list. Modifying
subject.
Can QA please verify that despite Gecko's claim to be "expired," that it does
indeed function properly?

Can Rick Potts or someone else in the know explain that this is expected
behavior?

If it really does work despite being "expired," I propose updating the Gecko
Start Page and Release Notes to document this as a bug, and explain that an
updated build will be available in February when we had originally planned for
this time bomb to expire. Thoughts?
paulmac - checking bug now....hang tight....he's the man!
Unfortunately, the time bomb is working correctly (however prematurely). You can
only surf to the netscape.com domain. Anywhere else won't let you load the page.
Whoops. So we need to get this fixed and posted.

This is for both ngt.exe and viewer.exe.
the build I have still looks good to me.

I think its a build from dec. 3.

I can go to http://www.yahoo.com and other sites
with no problem on my win95 laptop.

I've up the build on http://grok/u/chofmann/seamonkey.zip
can someone try this out and see if they get the same..
the build I have still looks good to me.

I think its a build from dec. 3.

I can go to http://www.yahoo.com and other sites
with no problem on my win95 laptop.

I've up the build on http://grok/u/chofmann/seamonkey.zip
can someone try this out and see if they get the same..
I used the Dec 4 build off sweetlou and paulmac used the Dec 4 download from
mozilla. Both of us had the problems he described.

The Dec 3 build was not the final DevPrev build.  I checked yours and yes, it
works.  But you have xpviewer as the exe, and we changed the name to ngt with
the Dec 4th and final DevPrev build.  So, what folks have on their floppies and
the one we posted to mozilla is indeed the build with the problem.
Hi.. I just downloaded the win95/nt binary from mozzilla. Im getting the time
bomb to when I run ngt.exe I wont let me surf.. Hope this helps
Ok, I'll recommend that DevEdge do the following:

1. Pull the download link to the Developer Preview build
2. Update the Gecko Start Page to contain a paragraph explaining the problem
3. One of the following:
   a) Encourage users to download the latest nightly seamonkey build
from              mozilla.org
   b) Tell users to wait for a new release "coming soon"

I need feedback from chofmann and chriss (and others) on 3a vs. 3b.
Assignee: cyeh → angus
Status: REOPENED → NEW
QA has verified that although the Dec 3 build doesn't have this problem, it
doesn't have any form of a timebomb that works. So, here's the current
recommendation:

1. Note on the Gecko start page that the current release has expired and as a
result, it will work only on netscape.com URLs or on the built-in sample files,
or other files residing on the local computer. We will also explain that an
updated version of the release will be available in February.

We may additionally explain that for those who are particularly adventurous, a
nightly build, which is much less stable, is available every day on mozilla.org.
We won't link directly to the download, but will instead link to the mozilla.org
binaries page which provides a scary warning.

Any objections to this plan?
I agree that this is what we should do.  Currently the start page has been
changed to say "a newer version coming".  This needs to get corrected ASAP.
lets do it!
Currently checking Dec 3, Dec 3a and Dec 4 builds for fileset diff.  Will decide
on replacement of Dev Prev after the the results are in.
So, where are we on this.  Did Angus pull unneeded files and wehave a new build
for QA to check?
I have pulled the files and am extracting the unneeded stuff, checking to make
sure it works in a safe directory (so when I rezip, it doesn't get _my_ cache
:-). I'll have something for QA to check at 12:30 pm today. If we send to
DevEdge tonight, it should be live tomorrow morning.
I have pulled the files and am extracting the unneeded stuff, checking to make
sure it works in a safe directory (so when I rezip, it doesn't get _my_ cache
:-). I'll have something for QA to check at 12:30 pm today. If we send to
DevEdge tonight, it should be live tomorrow morning.
Will put together QA testers. cyeh, please send build-ready announcement to
marvin-qa.
clarification: bits need to get to me, not dev-edge. the ftp url is served off of
the mirrored public ftp sites, which i control.  just let me know which bits to
grab, and they will get pushed and mirrored inside of a few hours.
Status: NEW → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Okay, this bug can (finally) be closed. Good job. :-)
Inserting Milestone info.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.