I assume that there are good reasons why the current release is stalled (GHC update, Cabal update?, ..), but such reasons are not easily visible on the platform web pages. Nor can I see any message traffic on this list that would discuss or explain the issues related to this delay (since "early April").From what I heard, I should wait for GHC 6.12.3. Anything else?We need to wait for GHC 6.12.3 -- due to the bug in 6.12.2
Thanks for the confirmation. But that is exactly the kind of information that HP downloaders would want to see on the HP pages (plus some indication of how uptodate it is and when to expect more news). Internal communication (even if there is a lot of it) is not the same as external communication.
More generally, could the current status of the platform please be made *obvious early* on its webpages? Currently, a visit looking for such info might go like this:Your plan sounds excellent. Do you think you could draft a page? I can add it to the site.
My "plan" was little more than a request that the HP release managers make the information you have (and I have not) available on the HP pages. I'm not a graphics designer, you do not need a draft for adding a link to a web page, and I do not have the information that I would
like to see on the pages. Which is why I was asking for that information in the first place!-)To make some progress, I attach a modified download page/style file (I'm not a fan of pixel-positioned HTML, so my attempt to fit the modifications into the layout might need adjustments). The idea is simply to have a single dated news item that lists current and next release versions, either with date or with reasons for delays, and to add a link to the release timetable for more detailed information
(since the platform logo is used elsewhere, it might be good to provide a variant with automatically overlaid version number). If you read the rest of my "plan", you'll notice that other pages will be affected, too (eg, the timetable should mention 6.12.3, not 6.12.2,should explain the reason for the delay, and should list any other tickets that are blockers for the release, or that are going to be fixed in that release; and the OS-specific versions should mention
the beta status and the kind/severity of the blocking issues - linkingto trac tickets would do). Having a delay is not the problem, not having information about it is.
Those changes are not cosmetic, they are about establishing a workflow that allows you (who have the information) to make current information available to HP users and to keep that info
up to date. Since you are already using trac, the simplest approachmight be to ensure that its features are put to good use. You would need to scan the tickets (at least once per release) to make sure that milestones are accurate, but then you could simply put a link to a custom trac query into the release timetable page (before the GHC team finally got overwhelmed by tickets, they had a good handle on using trac for this). Alternatively, the
wiki/trac integration should allow to list the most important tickets, and have them striked out as soon as they are closed. It is not about fiddling with the webpages now, to add todays info - that will only help for a few weeks. It is about making sure that the relevant information is maintained in the system,in such a way that it is published automatically or at least available to be queried.
ClausTitle: Download Haskell
Comprehensive
A rich development environment for Haskell
programming.
Robust
Stable and widely-used tools and libraries.
Cutting Edge
Advanced features such as easy multicore parallelism
and transactional memory.
Learn more...
News (21/05/2010):
The current release is 2010.1.0.0 beta.
The next scheduled release is 2010.2.0.0 (just waiting for release
of GHC 6.12.3).
html, body, div { margin:0; padding:0; }
body { padding-top: 150px; font-family: Helvetica, Arial, sans-serif;
font-size: 1em}
#download_bar {
background:url(background.png) repeat-x;
height: 253px;
position: relative;
}
#download_bar #logo {
position: absolute;
margin-left: -417px; /* 365 `div` 2 */
left: 50%; top: 0;
}
#download_bar #timetable {
position: absolute;
margin-left: -417px; /* 365 `div` 2 */
left: 50%; top: 80%;
}
#download_bar .wrap {
position: absolute;
margin-left: -200px; /* 400 `div` 2 */
left: 50%; top: 0;
width:400px; height:253px;
background:url(download.png) no-repeat;
}
#download_bar .info {
position: absolute;
margin-left: 230px;
width:250px;
left: 50%; top: 40px;
font-weight: bold;
font-size: 0.9em;
}
#download_bar .info .points {
margin-left: 20px;
font-weight: normal;
margin-bottom: 10px;
font-size: 0.9em;
}
#download_bar h1 {
position: absolute;
font-weight: normal;
top: 20px;
left: 0;
width: 400px;
text-align: center;
font-size: 2em;
color: #1c3a4b;
whitespace: nowrap;
}
#download_bar h2 {
position: absolute;
font-weight: normal;
top: 70px;
left: 0;
width: 400px;
text-align: center;
font-size: 1.15em;
color: #1c3a4b;
}
img { border: 0; }
a { color: #1c3a4b; }
a:hover { color: #1030cd; }
#download_bar .platforms a {
font-size: 0.9em;
border: 0;
position: absolute;
display: block;
top: 120px;
width: 100px; height: 20px;
padding-top: 80px;
text-align: center;
vertical-align: bottom;
}
#download_bar #osx { left: 30px; top: 120px; }
#download_bar #windows { left: 145px; top: 120px; }
#download_bar #linux { left: 267px; top: 120px; }
#releases {
float: left;
font-size: 0.9em;
font-style: italic;
border: 0;
padding-right: 20px;
padding-top: 4px;
text-align:left;
vertical-align: bottom;
}
#contact {
font-size: 0.9em;
border: 0;
padding-right: 20px;
padding-top: 4px;
text-align:right;
vertical-align: bottom;
}
_______________________________________________ Haskell-platform mailing list Haskell-platform@projects.haskell.org http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform
