You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Grant Ingersoll (JIRA)" <ji...@apache.org> on 2010/11/08 21:40:12 UTC
[jira] Created: (SOLR-2223) Separate out "generic" Solr site from
release specific content.
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (SOLR-2223) Separate out "generic" Solr site from
release specific content.
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (SOLR-2223) Separate out "generic" Solr site from
release specific content.
Posted by "Grant Ingersoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930173#action_12930173 ]
Grant Ingersoll commented on SOLR-2223:
---------------------------------------
The problem here is there is one and only one release specific doc. It seems like a waste to move things around for one doc, but I suppose it is still worth it since there isn't a clean way to do it now.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (SOLR-2223) Separate out "generic" Solr site from
release specific content.
Posted by "Grant Ingersoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930178#action_12930178 ]
Grant Ingersoll commented on SOLR-2223:
---------------------------------------
Here's what I propose to do:
# Move main site to https://svn.apache.org/repos/asf/lucene/solr/site
# Keep tutorial and release content where it is
# Update the release packaging to bring in the non-release content as part of a release
# Fix the docs on how to deploy it.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (SOLR-2223) Separate out "generic" Solr site from
release specific content.
Posted by "Grant Ingersoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930284#action_12930284 ]
Grant Ingersoll commented on SOLR-2223:
---------------------------------------
Yes, Hoss, that would make sense. I was just trying to do the least amount of work now for LUCENE-2746 to satisfy the needs there before we move to the new CMS.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (SOLR-2223) Separate out "generic" Solr site from
release specific content.
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930314#action_12930314 ]
Hoss Man commented on SOLR-2223:
--------------------------------
I don't really understand why this blocks LUCENE-2746 ? the solr "site" snapshot has always refered to "trunk", not the release - it's something we've talked about changing to mimic the way lucene-java had release specific tutorials/docs but never got around to.
Adding the TMs and consistent project name verbage to the site where it lives in svn right now and publishing should be just fine for satisfying LUCENE-2746 - no need to revamp how we build the site if we're just going to revamp it again using the CMS.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org