Here's the place to submit information to be included in Release Notes, and corrections to information already there. The URL for the Release Notes will be added to this bug as soon as a first draft is available. GUIDELINES: Please record ALL the information needed for the item you want documented. For example: BAD: "Add procedure for washing a cat to the Release Notes." GOOD: "Add procedure for washing a cat: (1)fill the sink; (2)put on gloves; (3)catch the cat..." (etc.)

<Are we just including Apprunner items in this bug, or also Viewer items? beppe mentioned that there was going to be a second developer release still using viewer, but this bug is in the Apprunner component. ;>

Please record notes for Viewer as well as Apprunner -- thanks.

Suggestion: vera, could you put link to working page of Release Notes in the URL field above. This way folks can check if their note is in first before adding another request for the same notes in the bug over and over. Should work easier for ya.

dp has a release note item for http://bugzilla.mozilla.org/show_bug.cgi?id=3690

You'll find the release notes (working draft) at this URL: http://twain.mcom.com/client/infodsgn/seamonkeyrelnotes.html (Note: The release notes are currently pretty empty; awaiting input)

If you have many local folders, you don't want to point the dogfood mail app at your real local folder hierarchy. We reparse all the folders at startup, and consume vast quantities of memory.

I'd note in the Release Notes that --- within Viewer --- virtually all of the menu items on the Debug & Tools either do nothing, do not work, or will invoke an application crash crash, as do several items on the File menu.

Please see bug # 3367 - if this gets fixed, you can ignore my comment. My comment was basically to point out that if you have lots of folders (say, dozens) with hundreds or thousands of messages, running the dogfood release will be painful. It's basically the total number of messages in all your folders that will get you.

The document at this link tells the user what functionality is in the dogfood mail release: http://www.mozilla.org/mailnews/smoketest.html Do you want to add this to the "limited features" section of your release notes? The document at this link tells the user what is needed to set up to run dogfood mail. http://slip/projects/seamonkey/mail/admin/dogfood_mail_startup.html You may wish to take items from this to put into your release notes. Note that this document can be changing, depending on our daily builds. Suggest you take the contents of this document towards the end of the week to put into the release notes.

"There are no keyboard shortcuts / command key equivalents for menu items in this preview release on any platform."

Please mention the following two preferences: 1. To get warning prompt before saving username/password or form data, set the following preference (by hand) in your prefs.js file: user_pref("wallet.useDialogs", true); By default that pref is false so the saving will be done silently. This is done because there currently are no dialog boxes and the warning prompt would occur in the console window. Since most users won't even know about this window, they will think the browser has hung. In the final product, with real dialog windows available, this preference won't exist and you will always be given a prompt before saving. 2. To suppress saving of form data altogether, set the following preference (by hand) in your prefs.js file: user_pref("wallet.captureForms", false); This preference is true by default. 3. To supress saving of username/password, set the following preference (by hand) in your prefs.js file: user_pref("network.singon.rememberSignons", false); This preference is true by default.

Editing in Mail Compose: * The cursor does not appear in the message field until you first start typing. * At the end of a line, you may need to hit ENTER twice before you the cursor moves to the next line. * The received message does not wrap lines, so you will probably want to put in hard returns in your messages. * We have a known problem with either having too much vertical white space or not enough.

attempting to launch the javascript console under the Tools menu in the viewer application freezes or crashes the machine. Fix for bug http://bugzilla.mozilla.org/show_bug.cgi?id=2326 did not make it for M3.

Please see bug #3646

In the "Preferences to run mail..." paragraph under section: "Limited support features" - please add the line to the top of the preferences list: user_pref("browser.download_directory", "C:\\TEMP\\");

Under "known issues": If you are unable to send mail, make sure that the directory specified in your prefs.js file under: user_pref("browser.download_directory", "C:\\TEMP\\"); actually exists.

unfortunately, the unix install instructions are not that simple at all. first, you need to make sure you have libgtk+ and glib version 1.2 installed (each of which requires several other libraries and packages to be up to date.) they are available from ftp.gnome.org or one of it's mirrors. second, the method of distribution for linux/unix is .tar.gz and not .zip. also, two environment variables must be set: MOZILLA_FIVE_HOME and LD_LIBRARY_PATH. so the new instructions should read (bearing in mind that i am not a technical writer): 1. create a directory named mozilla. move the tar.gz file into the mozilla directory. 2. Change to the mozilla directory (cd mozilla) and untar the archive (gzip -cd mozilla-i686-pc-linux-gnu.tar.gz | tar -xvf -). This will create a directory called package. 3. cd into package. type (pwd) and remember the result; you will need it for steps 4 and 5. it might look like: /home/me/mozilla/package 4. if you are running tcsh or csh, type ( setenv MOZILLA_FIVE_HOME RESULT_OF_STEP_3 ) and then type ( setenv LD_LIBRARY_PATH RESULT_OF_STEP_3:/lib:/usr/lib ) 5. or if you are running bash, sh, or ksh, type ( export MOZILLA_FIVE_HOME=RESULT_OF_STEP_3 ) and then type ( export LD_LIBRARY_PATH=RESULT_OF_STEP_3:/lib:/usr/lib ) 6. now (cd ..) and create a directory named user 7. cd into user and type ../package/apprunner

In the latest release notes under Mail Win32 Instructions: Change step 4 to read: 4) You can bring up Messenger using any of these methods: a) from command line using this argument: -url resurce:/res/samples/mailshell.xul b) or, from within apprunner's UI under Tasks | Messenger c) or, from command line using -mail argument --- In the latest release notes under Mail Win32 Instructions: In step 5, take out the line: "Or, you should also be able to bring up mail from within apprunner, under the Tasks menu." --- In the latest release notes under Mail Win32 Instructions: "Files Created or Used" section should be more prominent. Right now, it appears that this section is part of Mail Win32 instructions, which is not true. -- In the latest release notes under Limited Support Features: In the Available Mail/News Functionality Table: Take out the last two rows for "Reply to Message" and "Forward Message" which are not yet implemented.

Add: Back button doesn't work with manually entered URLs

Add: Stop button does not always work.

Add: Close menu item does not work. Close box works.

Add: Print and Print Preview not implemented.

Add: May have loading problem on pages which have applets. Possible crash or freeze.

Add: Floppies inserted while Apprunner is running are not mounted

Download instructions for Macintosh users: There are two possibilities, you either have Stuffit Expander™ installed and your web browser configured to use it or you don't. If you do: 1. Click once on the mozilla-mac.sea.bin link. The file will be downloaded to your default folder (usually the desktop) and Stuffit will start up and convert it to mozilla-mac.sea for you. Then stuffit will open up mozilla-mac.sea and convert it to a folder called mozilla-mac for you. 2. Inside the mozilla-mac folder will be a file called 'apprunner'. Just double-click and you are all set!(you can throw away mozilla-mac.sea and mozilla-mac.sea.bin) Note*If you try step one and your browser asks you what you want to do it's because you don't have Stuffit™ configured like you thought you did. No worries, just select 'save' continue from Step 3 below. If you do not have Stuffit Installed or your browser properly configured: 1. You must have Stuffit™ somewhere on your hard drive. 2. Click and hold the mozilla-mac.sea.bin link. Choose "Save this link as...". 3. A file dialog box will appear and you can select where you want to save the file, I recommend the Desktop. Click save. 4. Double-Click on the newly created icon that says mozilla-mac.sea.bin. 5. Stuffit™ will start up and simultaneously create mozilla-mac.sea and a folder called mozilla-mac. Inside the mozilla-mac folder will be a file called 'apprunner'. Just double-click and you are all set! (you can throw away mozilla-mac.sea and mozilla-mac.sea.bin)

I'm off to dinner, so I've posted the latest draft(see URL above). Please review and comment, I will check my email when I get back. If you decide to modify the release notes on your own, please note your change in this bug report. Thanks!

Here's the Win32 install info..... Download instructions for Windows users: You will need a copy of WinZip. This is shareware available at www.download.com. 1. Click once on the mozilla-win32.zip link. The file will be downloaded to your default folder. 2. Click on the mozilla-win32.zip file to launch WinZip. 3. After clicking on "I Agree" to terms of WinZip shareware, click on Extract in the WinZip tool bar. An x86 folder with application and associated files will be unzipped. 4) Select Apprunner from x86 folder and off you go!

I've posted the first draft to there home on mozilla for the early downloaders. Will update as needed.

modfied release notes to change the date and include Jan's Win32 instructions, and posted them to twain. I will check mail throughout the weekend in case any additional info needs to be modified/included.

Added new information on Gecko from Eric Krock, posted new draft of release notes on Twain. Please update on mozilla server. Thanks!

corrected typos in Unix install instructions and posted onto Twain.

Rockin...Let's call this puppy done and mark Verified. Simone, if all is cool...do you want to do the honors? :-)

Okay, I had one more piece of intruction to add re: Mac bookmark files. Updated on Twain, please post on mozilla. Then I can close this puppy! :-)

womped 'em @ 8:30p on 3/22

We be closed, then!

Well, this is the gift that just keeps on giving! The Int'l folks wanted to add some updated information which I got late last nite, so I've added that and posted a new file to Twain. I've also re-opened this bug but I'm not sure if that was The Right Thing To Do. Please advise (and post the new stuff to mozilla). Thanks!

Setting to Resolved/Fixed. Let's mark Verified in a few days when we are sure the last updates are done and we can verify that they are accessible.

womped latest at 4:00p 3/23. ekrock asked for updates to add startup instructions for viewer as well as the the ones we have for apprunner. If we do another round lets add that. if we leave this bug open its easier to find...

- Please explain how to start Viewer on Mac. - Please explain how to start Viewer on Linux. (Win32 explains how to start each; Mac/Linux should match.)

FOR MAC!! Need to add to first section 'or viewer'.....example.... 2.Open the mozilla-mac folder and double-click the file "apprunner" or "viewer" (Note: you no longer need the .bin files.) Need to add to second section 'or viewer'.....example 7.Open the mozilla-mac folder and double-click the file "apprunner" or "viewer" (Note: you no longer need the .bin files.) FOR UNIX!! Need to add to step #8: 8.Change to directory "user" and type ../package/apprunner OR ../package/viewer

One more request: the install instructions for Linux don't explain the relationship between the nspr.rpm and browser.rpm downloads. I'm am told both are necessary, and our download page on DevEdge Online reads as follows: - Win32 Install Zipfile with Fullcircle (allows transmission of crash data back to Netscape for analysis and posting to mozilla.org) - Mac 8.5 Install .bin - Linux: install both the nspr (.rpm file of Netscape Portable Runtime) and the browser (.rpm file) (see the full DP2/M3 release notes on mozilla.org) ... but the Linux instructions don't mention both of these or how they relate. Please edit the Linux instructions to make the install procedure, steps, and relationship of nspr.rpm/browser.rpm explicit. Thanks!

Linux steps per Mike McCabe: he doesn't claim to be an expert but has done this: 1)download both: a) nspr rpm file: ftp://ftp.mozilla.org/pub/mozilla/releases/m3/RPMS/opt/nspr-pthreads-3.1-SeaMonk ey_M3_BRANCH_19990323.i386.rpm b) browser rpm file: ftp://ftp.mozilla.org/pub/mozilla/releases/m3/RPMS/opt/mozilla-5.0-SeaMonkey_M3_ BRANCH_19990323.i386.rpm 2) become superuser 3) rpm -i NAME_OF_FIRST_FILE NAME_OF_SECOND_FILE ---- We need this checked/elaborated by an authoritative Linux install expert ASAP. Added leaf to cc: list temporarily as he's said to know this.

I added the apprunner and viewer insructions to both Unix and Mac sections. Since we haven't heard confirmation from Leaf, I didn't add the additional Unix instructions. The latest draft is posted on twain, please push to Mozilla. I'll be on vacation until Tuesday, but Vera can update the notes if need be.

I think we're all done writing release notes for M3. Closing bug.

marking Verified...yep this milestone is history baby!!!

Moving all Apprunner bugs past and present to Other component temporarily whilst don and I set correct component. Apprunner component will be deleted/retired shortly.