> 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
