Two suggestions/comments: 1) First, after thinking about it over night, I think the property should only have one value and that's the (minimum) build number to which the documentation applies. This would make things very simple and easier to maintain.
2) Second, I think Craig raises a much more fundamental question which is where the "truth" for "developer" documentation should live, on flexwiki.com or under version control. I have to admin that I have a strong initial reaction to the idea that the source of truth should be the version control system. That would mean, as Craig said, that the documentation could only be changed by developers on the project. Maybe we haven't defined what types of pages we're actually talking about here, but that seems like a big problem because it excludes people who are not developers on the project improving the documentation with examples, better explanations, links to related topics, etc. Even worse, the side effect of that is to increase the responsibilities of our very strapped dev team of today ;-) I'll admit that this is just my first knee-jerk, so perhaps someone can help me think about this differently. What the problem that keeping the "documentation" pages in SVN would solv e? And what do we mean by "documentation" pages? /David > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:flexwiki- > [EMAIL PROTECTED] On Behalf Of Craig Andera > Sent: Thursday, September 13, 2007 5:03 AM > To: 'FlexWiki Users Mailing List' > Subject: Re: [Flexwiki-users] Documentation idea > > > I don't believe marking the documentation with properties such as > > these will cause any issue with operating as you suggest. This would > > allow us to have one body of documentation in SVN and make it clear > if > > the documentation applies. > > > > Additionally if a new feature is added then after release if could > look > > like: > > > > DocumentationForVersion: 1.0.0.1677, 2.0 > > > > and this would still work with > > > > .Contains("1.0') selection criteria. > > Fair enough, but I think it's highly unlikely that anyone is going to > go > through and maintain the version number metadata. Someone might for a > while, > and then it'll just sort of...not happen any more. > > On the other hand, I think it's much more reasonable for a developer to > every once in a while go through all the documentation on their local > box > and make sure it applies to the version they're working on. > > > > ----------------------------------------------------------------------- > -- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Flexwiki-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/flexwiki-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flexwiki-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flexwiki-users
