Hi Hannes,
So, here is my left handed pet dwarf turtle, born in December, idea:
It doesn't really see the point of scattering boxes all around. One
box listing current php5 + php4 version and the current release
candidates should be all that we need.
The RC links obviously won't be direct links on the tarballs so the
user still has a chance of understanding "wth is RC?".
The release candidate links will point to qa.php.net/#v5 & #v4 where
we'll add a big fat box explaining the concept of release _candidate_.
The stable links then point to php.net/downloads.php#v5 & #v4
The only "major" change is how RM will post a new release; this patch
expects all current (stable and (if any) rc) in include/version.inc
See attached, simplified, patch & screenshot:
http://home.oslo.nith.no/~maghan/releases.png
We can then provide a Atom+SLE feed with latest versions with direct
links to the stable releases and a link to qa.php.net with RCs....
If I am totally off base here, scream :)
My right handed pet killer rabbit, born in July, quite likes it :) but
noticed that you didn't make that conference/cfp block at the top happen
yet...?
- Steph
-Hannes
--------------------------------------------------------------------------------
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
