I realise that the apachesolr developers have decided to abandon the 6.x-2.x branch and instead move to a future 6.x-3.x branch. I appreciate that there are likely very good reasons for this, however I am hoping I can persuade you to make minor changes in the transition process that I feel will help users currently on the 6.x-2.x branch.

Rather than flagging the 6.x-2.x branch as unsupported it would be preferable, IMHO, if you left is as it had been, but updated the module's page to make it abundantly clear that the 6.x-2.x branch has been abandoned and will not be receiving any updates and that new users should use 6.x-1.x until 6.x-3.x comes out. Then, when 6.x-3.x comes out, mark 6.x-2.x as unsupported.

The reason I think this is a preferable way to go is because people currently on 6.x-2.x are stuck with either staying where they are, or reverting to 6.x-1.x and losing the feature that brought them to 6.x-2.x in the first place. Unsupported doesn't necessary mean insecure, so those who value the extra features may prefer to stay where they are, but there will be no way to know if a security vulnerability is found in the module at a future time.

Comments

pwolanin’s picture

pwolanin commented

Leaving the branch supported at all implies someone is paying some amount of attention to bug reports and other issues, even if only to asses whether they are security vulnerabilities or other critical problems.

No one has stepped up to do that, so marking it as unsupported is the only honest approach, I think.

pwolanin’s picture

pwolanin commented
Status: Active » Closed (fixed)