Closed Bug 815820 Opened 9 years ago Closed 9 years ago

Fix SeaMonkey 2.14 README on ftp server on how to get the source code

Categories

(SeaMonkey :: Build Config, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mcsmurf, Assigned: ewong)

Details

(Whiteboard: [good first bug][lang=English][mentor=Frank Wein :mcsmurf])

Attachments

(1 file)

The README file for SeaMonkey 2.14 includes wrong instructions for how to get the source code (ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/2.14):
"These binaries were all built from mozilla's comm-central Mercurial repository,
off the SEAMONKEY_2.14_1_RELEASE tag, with the following commands used to obtain
the source:

  hg clone -r SEAMONKEY_2.14_1_RELEASE http://hg.mozilla.org/releases/comm-release
  cd comm-release
  python client.py checkout --rev=SEAMONKEY_2.14_1_RELEASE"

The README should either say SEAMONKEY_2_14_BUILD1 or SEAMONKEY_2_14_RELEASE as the SEAMONKEY_2.14_1_RELEASE tag does not exist.
Whiteboard: [good first bug][lang=English][mentor=Frank Wein :mcsmurf]
Is this something that's done directly on the ftp site, or is this
through some Makefile?
Assignee: nobody → ewong
Status: NEW → ASSIGNED
Attached file Updated README file.
Attachment #695081 - Flags: review?(bugzilla)
Comment on attachment 695081 [details]
Updated README file.

Looks good, but not sure if this README is automatically generated. I could not find out where it's coming from..
Attachment #695081 - Flags: review?(bugzilla) → review+
(In reply to Frank Wein [:mcsmurf] from comment #3)
> Comment on attachment 695081 [details]
> Updated README file.
> 
> Looks good, but not sure if this README is automatically generated. I could
> not find out where it's coming from..

It's generated during the release process.  Once released, iirc, I need to
go into the ftp directory and manually edit it. :)
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.