SeaMonkey System Requirements need update

RESOLVED WORKSFORME

Status

defect
RESOLVED WORKSFORME
4 years ago
Last year

People

(Reporter: RainerBielefeldNG, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

()

Attachments

(1 attachment)

I doubt that users can enjoy SeaMonkey with recommended 
* 128 MB RAM
* 50 MB of free hard drive space

;-)

We should make system requirements version dependent, may be
* Before SM 2
* SM 2.0 and later
* SM 2.35 and later

(no need for more steps before 2.35)
I think that the "system requirements" page should reflect the requirements for currently supported versions, i.e. currently 2.38 and later. (We want to encourage users of older versions to update to a current version if they possibly can, don't we?) If the requirements increased a lot at a recent time, the fact can perhaps be mentioned in smaller type; maybe in a footnote.

IMHO anything before SeaMonkey 2 (i.e., before the Toolkit Transition) is irrelevant today, and the relevancy of the builds from the Toolkit Transition to the start of the Release Train is doubtful to say the least.

See also https://en.wikipedia.org/wiki/SeaMonkey#Release_history
See Also: → Sm_tri_HowTo
See Also: → 1257256
Product: Websites → SeaMonkey
(In reply to Rainer Bielefeld from comment #0)
> Created attachment 8666439 [details]
> Screenshot with comments
> 
> I doubt that users can enjoy SeaMonkey with recommended 
> * 128 MB RAM
> * 50 MB of free hard drive space
> 
> ;-)
> 
> We should make system requirements version dependent, may be
> * Before SM 2
> * SM 2.0 and later
> * SM 2.35 and later
> 
> (no need for more steps before 2.35)

Who has got the system requirements info?
Flags: needinfo?(RainerBielefeldNG)
For current SM information on that page seems ok. WFM for now.

I don't know whether system requirements page still reflects requirements for latest trunk.
Status: NEW → RESOLVED
Closed: Last year
Flags: needinfo?(RainerBielefeldNG)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.