Katie Capps Parlante wrote:
Not to throw a last minute curve ball or anything, but I wanted to
bring up a minor problem...
These two links have time-specific information, that will go out of
date or change with the next release:
http://chandlerproject.org/Projects/KnownIssues
http://chandlerproject.org/Projects/ReleaseNotes
I don't think the right thing to do is to just edit the same page
pages when we are filling out issues and release notes for the next
releases. I think we ought to preserve the information about the 0.7
release. Also, after Preview, the releases of Chandler Server and
Chandler Desktop will not be coordinated and follow separate
lifecycles, so combining these pages for both won't make as much sense.
Proposal: Rename to PreviewKnownIssues and PreviewReleaseNotes?
Sure, so that we have a known archival system. Also it makes sense to
have the application pointing to its specific release note page rather
than to a newest (and potentially irrelevant) page.
That being said, we can still have permanent Projects/KnownIssues and
Projects/ReleaseNotes always redirecting to the latest and greatest.
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
