Brian Aker wrote:
Why not just update the wiki on code.google.com? A greater number of
people can access/keep that up to date.
I probably agree with you there. I'm one of those people (though I
can't seem to be able to edit the summary). code.google.com does have
the release notes and such, but not necessarily the most user friendly
summary page. Users are looking for what it is, what's the latest
release, and where to get it. It's all there on danga.com (but
incomplete) and one has to dig for it on code.google.com.
Reality is a bunch of things on danga.com point to code.google.com
already. I'm not sure what the right way forward is but even if there
were a decision to do that, someone would need to update danga.com.
We can probably come up with a better long term plan in some kind of
face-to-face discussion at OSCON, but for the short term just getting
the release notes link on the news page on danga.com will probably help.
- Matt
On Jul 16, 2009, at 9:53 AM, Matt Ingenthron wrote:
Based on a discussion on the IRC channel and the mailing list, it
seems people aren't finding the release notes. I believe (partially
because one guy told me it was the case) this is because the release
notes are not linked from the danga.com/memcached/news.bml page
When walking around, danga.com/memcached/apis.bml also seems to point
to only the old protocol.txt in subversion. It's not up to date with
the 1.4.0 release and it doesn't mention the protocol-binary.xml
which should probably be cooked and hosted somewhere. Perhaps I'll
do that for 1.4.0 and put it on the wiki for a danga.com pointer.
- Matt
