Just rolling the 6.x-1.3 release. This issue will serve as a meta-issue to define and track work to be done for a 6.x-1.4 release as a follow-up to #1098954: Short-term roadmap for 6.x-1.3 release.

Comments

jpmckinney’s picture

jpmckinney commented

Possibilities:

#594068: Deleting of taxonomy terms doesn't trigger index update
#985484: Core Search Indexer should be turned off automatically
#881760: account for http://drupal.org/node/345591
#494182: apachesolr and core search treat Drupal fields (Field API, CCK) differently

pwolanin’s picture

pwolanin commented

To be ported (easy):
#1098038: Did you mean - shouldn't be a <label> element

and maybe (harder):
#456420: Add Batch API support for rebuilding indexes

pwolanin’s picture

pwolanin commented
Title: roadmap for 6.x-1.4 release » roadmap for 6.x-1.5 release

Just released 1.4.

Changes since 6.x-1.3:

  • #881760 by pwolanin: remove status messages that are now supplied by Drupal core.
  • define an API version string
  • #761990 by jhedstrom, pwolanin: switch to POST for long search ULRs.
  • #1097988 by jpmckinney, pwolanin: minor config fixes, including Avoiding warning "No queryConverter defined"
  • #1163612 code comment cleanup
  • #1084332 by pwolanin, elliotttf: follow-up to add missing apachesolr.make
  • #1141046 by craig_: fix variable name for highlighting
  • #1146054 Remove unneded & (reference) operators for objects

We can use this issue to continue discussion for 1.5

pwolanin’s picture

pwolanin commented
Title: roadmap for 6.x-1.5 release » roadmap for 6.x-1.6 release

There were 2 critical bugs, so releasing 1.5 with just those:

  • #1167722 by pwolanin: fix for Drush command solr-index cannot be run.
  • #1138602 by pwolanin: fix for search block broken in certain block configurations.
geerlingguy’s picture

geerlingguy commented

I've been using the 2.x releases on a bunch of different sites, as some of the features were very helpful for different purposes... is there any particular reason why that version has been marked as unsupported? There is not yet a 3.x release, and 1.x is missing some of the features that were in 2.x.

I thought 2.x was originally going to be the main supported release, no?

pwolanin’s picture

pwolanin commented

no, the 2.x was never intended to be the main branch, as far as I know.

We will be working on the 3.x very soon.

pwolanin’s picture

pwolanin commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.