[
https://issues.apache.org/jira/browse/SOLR-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930241#action_12930241
]
Hoss Man commented on SOLR-2223:
--------------------------------
Given the dev merge of lucene/solr, and the reduction in subprojects due to
graduation, and the consideration of a using hte new CMS, now is probably a
good time to consider abandoning the way we've been having distinct svn paths
for the "site" of each subproject.
why not move to a single "site" directory in svn for the entire TLP that the
CMS updates (which can still have subdirs by project and what not, but can
easily maintain a consistent navigation and look and fell) and then keep only
the releases specific docs in the individual sub-proj trunk dirs?
> Separate out "generic" Solr site from release specific content.
> ---------------------------------------------------------------
>
> Key: SOLR-2223
> URL: https://issues.apache.org/jira/browse/SOLR-2223
> Project: Solr
> Issue Type: Task
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Priority: Minor
>
> It would be useful for deployment purposes if we separated out the Solr site
> that is non-release specific from the release specific content. This would
> make it easier to apply updates, etc. while still keeping release specific
> info handy.
--
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: [email protected]
For additional commands, e-mail: [email protected]
