Okay, how about following layout:

----------
Downloads.

To use Squeak, you need to have two things: blabla

A current release is Squeak X.YZ.
Click here for release details.

- a single-click download of VM+image+sources for Win32
- a single-click download of VM+image+sources for Mac
- a single-click download of VM+image+sources for Linux
 --------

Releases

- Squeak 3.10 . Release date: XX-YY-ZZ
     This release is based on blablabla short descrition.
     Click for more details & downloads.

- Squeak 3.10 full . Release date: XX-YY-ZZ
     This release is based on blablabla short descrition.
     Click for more details & downloads.

- Squeak 3.X . Release date: XX-YY-ZZ
     This release is based on blablabla short descrition.
     Click for more details & downloads.

- Squeak VM Win32. Release date: XX-YY-ZZ
     This release is based on blablabla short descrition.
     Click for more details & downloads.

----
2008/5/9 Janko Mivšek <janko.mivsek at eranova.si>:
> Igor Stasenko wrote:
>>
>> Now, as Squeak 3.10 released and we have to update sites.
>> But there are critical bugs reported by Keith, like bug in TimeDate
>> and  incorrect version number.
>>
>> First, i propose to reorganize squeak.org and replace Downloads page
>> with Releases page.
>
> I think we better stay with Downloads page (everyone is used of
> Downloads name, specially newcomers are looking for such page first) but
> yes, let there be additional pages for each release with release notes etc.
> Downloads page holds therefore simply a current release while older releases
> are linked from that page.
>
> I also agree that we introduce patches, which are accessible directly from
> Downloads page (maybe even something like Service packs?). TimeDate and
> version patch for instance can be a first such patch.
>
>
>> Releases should have a list of links to pages with separate releases ,
>> where users can read more detailed information about release
>> and decide whether download it or not, or go back and pick another
>> release.
>>
>> Now, concerning a page, which describes a release.
>> It should contain a list key features and describe shortly what its
>> now includes, and what is changed comparing to previous release e.t.c
>> As well as provide a link to download & install release by single click.
>>
>> Also, separate page is good place to put critical fixes to base image.
>> And as with example of 3.10, a page can contain a link to
>> already released image, and then followed by patch list, which fixing
>> different critical bugs.
>>
>> This will make it easy for newcomers to update just downloaded image
>> without going deep with details, what is mantis or update streams.
>> They can just download & file in a change set.
>> Also, on a release page , user can see arguments, why he would need to
>> download it, or what it fixes.
>>
>> So, instead of single downloads page, we will have a tree of pages:
>>
>> Releases
>>  - 3.10
>>  - 3.9
>>  - 3.8
>>  - Linux VM
>>  - Windoze VM
>>  - Mac VM
>>  - squeak-dev 3.10
>>  - funSqueak
>>  - etc..
>>
>> I think this will make things more convenient for beginners and for
>> site support as well.
>> As well as allow to make better coverage & description of particular
>> release.
>>
>>
>
> --
> Janko Mivšek
> AIDA/Web
> Smalltalk Web Application Server
> http://www.aidaweb.si
>
>



-- 
Best regards,
Igor Stasenko AKA sig.