incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <chip.child...@sungard.com>
Subject Re: [DISCUSS][WIKI] Do we need a top-level Releases page?
Date Tue, 19 Feb 2013 15:02:42 GMT
On Fri, Feb 15, 2013 at 01:20:37PM -0600, Joe Brockmeier wrote:
> On Fri, Feb 15, 2013, at 12:52 PM, Alex Huang wrote:
> > Joe,
> > 
> > I think the pages for the releases in progress which updates users and
> > developers about the status, bugs, and features of a release in progress
> > should still be relatively high in the tree so people can easily access
> > it.  That's information that people don't have access to from the landing
> > page.  It doesn't have to be top level though.  You decide.  As for the
> > current release, we can probably remove it.
> 
> Sure - releases in progress definitely belong on the wiki, no question.
> That's fast-moving info that we need to edit almost daily. 
> 
> I just want to avoid duplicating content and having "stale" information
> in one place or another. So the "finished" releases should live on the
> main site because that information isn't going to change. (e.g., 4.0.0
> will always have been released on 11/6/2012)
>

As long as any meaningful content is appropriately kept (ex: design
docs, test plans, etc...).  I think that if the release pages are
limited to release planning and tracking, then we are fine cleaning them
up after a release is completed.

> > Very disappointed that we can't use the html exports.  Don't really
> > understand why from reading that page David sent out.
> 
> Sorry - the other issue he raised is pretty clear, though: To use the
> wiki as our "official" site, we'd have to lock down contributions to
> committers only, which would be bad on a number of levels. 
> 

Yup, it is what it is... ;-)

> Thanks for getting back on this quickly!
> 
> Best,
> 
> jzb
> -- 
> Joe Brockmeier
> jzb@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
> 

Mime
View raw message