You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Boris Kolpackov (JIRA)" <xe...@xml.apache.org> on 2008/02/21 12:11:19 UTC
[jira] Updated: (XERCESC-1784) Website support for Xerces-C++ 2 and
3-series
[ https://issues.apache.org/jira/browse/XERCESC-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Kolpackov updated XERCESC-1784:
-------------------------------------
Priority: Blocker (was: Major)
> Website support for Xerces-C++ 2 and 3-series
> ---------------------------------------------
>
> Key: XERCESC-1784
> URL: https://issues.apache.org/jira/browse/XERCESC-1784
> Project: Xerces-C++
> Issue Type: Task
> Components: Documentation
> Reporter: Boris Kolpackov
> Assignee: Boris Kolpackov
> Priority: Blocker
> Fix For: 3.0.0
>
>
> I think it will be a good idea to have online documentation (build instructions,
> API references, etc.) for both 2 (2.8.0) and 3 (3.0.0)-series. The reason for this
> is that 3.0.0 introduces a number of backwards-incompatible changes and I expect
> a sizable chunk of the user base to stick with the 2-series for some time.
> My idea on how to do this is to have two sets of "menu links" in the left "menu bar".
> One for 2.8.0 and one for 3.0.0 (some links, e.g., "Charter", "Release Info", "Feedback",
> etc.) are common for both releases and won't be in the release-specific sections. In
> other words, the menu will look like this:
> * Readme
> * Charter
> * Release Info
> * Download
> --------------
> 2.8.0:
> * Installation
> * Build Instructions
> * Programming Guide
> * Samples
> * FAQs
> * API Reference
> * DOM C++ Binding
> * Migration Guide
> -----------------
> 3.0.0:
> * Installation
> * Build Instructions
> * Programming Guide
> * Samples
> * FAQs
> * API Reference
> * DOM C++ Binding
> * Migration Guide
> -----------------
> * Feedback
> * Bug Reporting
> * Mailing Lists
> * Source Repository
> * Applications
> For this to work we will need to "divorce" the website source from the library source
> itself (which I believe is a good idea on its own) and put it into a separate SVN project.
> The complete website copy will then be built by using the release-independent part
> plus the release-specific parts from the latest releases of 2 and 3-series.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org