lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Commented: (SOLR-2223) Separate out "generic" Solr site from release specific content.
Date Tue, 09 Nov 2010 19:21:06 GMT


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:
>             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:
For additional commands, e-mail:

View raw message