on Fri Aug 08 2008, Beman Dawes <bdawes-AT-acm.org> wrote:
Can we expect developers (and other interested parties) to figure out that they need to look at a hidden site to find this information? And doesn't the fact that it's a beta mean that it could churn and make the results unavailable or wrong without warning? Shouldn't our most important testing results be hosted in a stable environment? It's common to have a "development" or "developers" link that takes you to materials about the unreleased code on the front page of a project's site.
Sounds like the current arrangement is not very user-friendly. Can we change it?
Good questions.
Is one of the consequences of separating web site content from release content is that this becomes a question for the web site team rather than the release management team?
I think it was always a question for the website team, if we ever had one ;-)
Perhaps we should explicitly identify who the web site team is, what their responsibilities are,
That's a good idea regardless. I nominate Rene ;-)
and where the dividing line is between release management and web site management.
I *think* it's less a question of dividing and more a question of how we decide what web material goes into the release. But, I'm not sure. -- Dave Abrahams BoostPro Computing http://www.boostpro.com