Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Gerhard Fiedler wrote: > Now that you say it... :) The way to get there goes through a link to a > "Development download page" (I wasn't looking for a development download) > and there it is located in the topic "Current versions". It could be better > advertised... Perhaps it should say 'Unstable/Testing Download'? I'm not very good at websites, as you can tell... that was part of my motivation for the wiki. Unfortunately it became susceptible to spam so I had to limit the editors (it's not very limited.. I basically just add anyone who asks, but it's not as free as it was). > Now that you say it... :) There's no link to either the history page nor > the blog from the Wiki main page or any of the download pages, at least not > that I could find it. I could have found it searching the wiki for > "history", but I guess I thought (not really very consciously) if something > like this existed, there would be a link from the main page or the download > pages. There should be a link on the main page. It's gone missing... > Why is all that information so scattered around, so badly linked? You have > the wiki already, can't you just put the history info there? People like the RSS feed, and the blog gives that for free. The history info was in the wiki but it wasn't really suitable for large release notes and parsing the RSS out of it was a nightmare (and I couldn't separate stable releases from unstable ones easily). > change history from one stable release to the next. (This supposedly would > be the addition of all incremental development builds between the two.) Or > do you compile this information into the change logs for the releases in > the "Stable" category? If so, this again is I try to put as much info in a stable release note as is needed to bridge the gap between the two releases. The list gets the shorter form, and the release notes plus history get the longer form. > Maybe a wiki page "Release Information", linked from the main wiki page, > that contains links to the pages with the collected release information? > One page per stable release. You collect the things you do in a page > "Current Development" (like you are doing in the blog) and once that > becomes a stable release, you rename the page to "Release 2.1.15" or > whatever? And add a link to the release files to it? That's possible... it's basically what the blog does though. > So there's no known problem with & (with or without watch/edit -- which I > also use) in any of the releases post 2.0.62? Not that I am aware of. Tony