Re: The state of Solr 5. Is it in maintenance mode only?

[Chris Hostetter]

: On the 5.x front I wasn't expecting 5.6 release now that we have 6.x but
: was simply surprised to see fix for 4.x and not for 5.x.

As Shawn mentioned: jira issues might have inccorrect fixVersion info if 
people don't pay enough attention when resolving (especially with 
dups/invalid) but what really matters is what gets committed/released.

Wether or not there are any future 4.x "bug fix" releases depends entirely 
on the severity of the bug and the demand from users for fixes -- 
particularly for security relatd bugs, you might see more effort put into 
backporting "farther back" in the release timeline and releasing a 4.10.x 
release.  

: As for adoption levels, it was my subjective feel reading this list. Do
: we have community survey on that subject? That would be really
: interesting to see.

As a developer, my focus is on building features and fixing any bugs found 
in the current major version release branch, w/o worrying too much about 
bugs that may only affect older previous major versions.  If someone finds 
a bug in 5.x, and that bug no longer exists in 6.x, I have less 
interested/motivation to look into that bug then something else that 
*does* affect 6.x, because there is already a fix/workaround available...

Upgrade to the latest version.

while some users might have (completley understandable) mitigating factors 
preventing them from upgrading, that doesn't really affect my 
interest/motivation in fixing bugs on older branches, because users who 
have reasons preventing them from upgrading to recent major versions 
frequently tend to have one thing in common: They have things preventing 
them from upgrading at all.

So even if i put in the effort to find/diagnose/fix an old bug, and even 
if the project as a whole goes to the effort to build/test/release from an 
"older" major version dev branch, the return on investment for that work 
is lower then putting the same amount of effort into bug fixes on a 
"newer" major version dev brach.

For example: let's say hypothetically the Solr user base was devided 
evenly into 3rds: 1/3 using 6.x.0, 1/3 using 5.y.0, 1/3 using 4.z.0.  In 
theory, if 3 diff bugs affect each of those 3 versions to the same degree, 
then the number of users impact by a 4.z.1 bug fix would same as the 
number of users impacted by a 5.y.1 or a 6.x.1 bug fix -- but in practice, 
the number of 4.z.0 users who are likely to upgrade to 4.x.1 is much lower 
then the number of 5.y.0 users who would upgrade to 5.y.1, which is less 
still then the number of 6.x.0 users who will upgrade to 6.x.1. 


-Hoss
http://www.lucidworks.com/

Re: The state of Solr 5. Is it in maintenance mode only?

[Charlie Hull]

On 28/11/2016 13:11, Jaroslaw Rozanski wrote:

Hi,

Thanks for elaborate response. Missed the link to duplicate JIRA. Makes
sense.

On the 5.x front I wasn't expecting 5.6 release now that we have 6.x but
was simply surprised to see fix for 4.x and not for 5.x.

As for adoption levels, it was my subjective feel reading this list. Do
we have community survey on that subject? That would be really
interesting to see.

Hi,

We still see Solr 4.x running in the wild, though not so often these 
days. 5.x is also common especially when running under other systems 
such as Drupal or Sitecore (the developers of these systems and others 
that integrate Solr will often get something running with whatever 
version is reasonably current - often a barely modified example config - 
then not touch it again for ages. We obviously recommend 6.x for new 
installations and encourage others to upgrade to this if possible. Note 
that this upgrade process gets harder the further you are away from the 
current release.


Cheers

Charlie



Thanks,
Jaroslaw


On 28/11/16 12:59, Shawn Heisey wrote:

On 11/28/2016 4:29 AM, Jaroslaw Rozanski wrote:

Recently I have noticed that couple of Solr issues have been
resolved/added only for Solr 4.x and Solr 6.x branch. For example
https://issues.apache.org/jira/browse/SOLR-2242. Has Solr 5.x branch
been moved to maintenance mode only? The 5 wasn't around for long
before 6 came about so I appreciate its adoption might not be vast.

The 5.0 version was announced in March 2015.  The 6.0 version was
announced in April 2016.  Looks like 4.x was current for a little less
than three years (July 2012 for 4.0).  5.x had one year, which I
wouldn't call really call a short time.

Since the release of 6.0, 4.x is dead and 5.x is in maintenance mode.
Maintenance mode means that only particularly nasty bugs are fixed and
only extremely trivial features are added.  The latter is usually only
done if the lack of the feature can be considered a bug.  There is never
any guarantee that a new 5.x release will be made, but if that happens,
it will be a 5.5.x release.  The likelihood of seeing a 5.6 release is
VERY low.

SOLR-2242 is a duplicate of SOLR-6348.  It probably had 4.9 in the fixed
version field because that's what was already in it when it was resolved
as a duplicate.  It's a very old issue that's been around since the 3.x
days.  No changes were committed for SOLR-2242.  The changes for
SOLR-6348 were committed to 5.2 and 6.0.  I have updated the fix
versions in the older issue to match.  The versions should probably all
be removed, but I am not sure what our general rule is for duplicates.

Thanks,
Shawn




--
Charlie Hull
Flax - Open Source Enterprise Search

tel/fax: +44 (0)8700 118334
mobile:  +44 (0)7767 825828
web: www.flax.co.uk

3rd party integrations (was: The state of Solr 5. Is it in maintenance mode only?)

[Alexandre Rafalovitch]

On 29 November 2016 at 00:24, Shawn Heisey  wrote:
> Third-party integrations (Solr support in other software) tend to be
> VERY slow to upgrade.  Some of them are still shipping configs designed
> for Solr 3.x, which won't work in 5.x and later.  Some are still
> shipping configs designed for 4.x, which frequently don't work in 6.x,
> and generate warnings in 5.x.

I wonder what the root cause of it is and how much effort would it be
to change the status quo. Is that an issue of somebody very familiar
with Solr trying those products together and reporting what needs to
be fixed and why?

Or are the integrations done super-sporadically and are basically
abandoned unless somebody steps in?

I'd love a range of opinions from the downstream users/implementors.

Regards,
Alex.
P.s. I am _presuming_ there is a value in the integrations using
latest Solr and therefore the version lag is a bad thing. Perhaps I am
wrong on that too.


http://www.solr-start.com/ - Resources for Solr users, new and experienced

Re: The state of Solr 5. Is it in maintenance mode only?

[Shawn Heisey]

On 11/28/2016 6:11 AM, Jaroslaw Rozanski wrote:
> As for adoption levels, it was my subjective feel reading this list. Do
> we have community survey on that subject? That would be really
> interesting to see.

That's really hard for me to say.  Users tend to not what version they
are running unless they're having issues.

Third-party integrations (Solr support in other software) tend to be
VERY slow to upgrade.  Some of them are still shipping configs designed
for Solr 3.x, which won't work in 5.x and later.  Some are still
shipping configs designed for 4.x, which frequently don't work in 6.x,
and generate warnings in 5.x.

Thanks,
Shawn

Re: The state of Solr 5. Is it in maintenance mode only?

[Jaroslaw Rozanski]

Hi,

Thanks for elaborate response. Missed the link to duplicate JIRA. Makes
sense.

On the 5.x front I wasn't expecting 5.6 release now that we have 6.x but
was simply surprised to see fix for 4.x and not for 5.x.

As for adoption levels, it was my subjective feel reading this list. Do
we have community survey on that subject? That would be really
interesting to see.


Thanks,
Jaroslaw


On 28/11/16 12:59, Shawn Heisey wrote:
> On 11/28/2016 4:29 AM, Jaroslaw Rozanski wrote:
>> Recently I have noticed that couple of Solr issues have been
>> resolved/added only for Solr 4.x and Solr 6.x branch. For example
>> https://issues.apache.org/jira/browse/SOLR-2242. Has Solr 5.x branch
>> been moved to maintenance mode only? The 5 wasn't around for long
>> before 6 came about so I appreciate its adoption might not be vast.
> 
> The 5.0 version was announced in March 2015.  The 6.0 version was
> announced in April 2016.  Looks like 4.x was current for a little less
> than three years (July 2012 for 4.0).  5.x had one year, which I
> wouldn't call really call a short time.
> 
> Since the release of 6.0, 4.x is dead and 5.x is in maintenance mode. 
> Maintenance mode means that only particularly nasty bugs are fixed and
> only extremely trivial features are added.  The latter is usually only
> done if the lack of the feature can be considered a bug.  There is never
> any guarantee that a new 5.x release will be made, but if that happens,
> it will be a 5.5.x release.  The likelihood of seeing a 5.6 release is
> VERY low.
> 
> SOLR-2242 is a duplicate of SOLR-6348.  It probably had 4.9 in the fixed
> version field because that's what was already in it when it was resolved
> as a duplicate.  It's a very old issue that's been around since the 3.x
> days.  No changes were committed for SOLR-2242.  The changes for
> SOLR-6348 were committed to 5.2 and 6.0.  I have updated the fix
> versions in the older issue to match.  The versions should probably all
> be removed, but I am not sure what our general rule is for duplicates.
> 
> Thanks,
> Shawn
> 

-- 
Jaroslaw Rozanski | e: m...@jarekrozanski.com



signature.asc
Description: OpenPGP digital signature

Re: The state of Solr 5. Is it in maintenance mode only?

[Shawn Heisey]

On 11/28/2016 4:29 AM, Jaroslaw Rozanski wrote:
> Recently I have noticed that couple of Solr issues have been
> resolved/added only for Solr 4.x and Solr 6.x branch. For example
> https://issues.apache.org/jira/browse/SOLR-2242. Has Solr 5.x branch
> been moved to maintenance mode only? The 5 wasn't around for long
> before 6 came about so I appreciate its adoption might not be vast.

The 5.0 version was announced in March 2015.  The 6.0 version was
announced in April 2016.  Looks like 4.x was current for a little less
than three years (July 2012 for 4.0).  5.x had one year, which I
wouldn't call really call a short time.

Since the release of 6.0, 4.x is dead and 5.x is in maintenance mode. 
Maintenance mode means that only particularly nasty bugs are fixed and
only extremely trivial features are added.  The latter is usually only
done if the lack of the feature can be considered a bug.  There is never
any guarantee that a new 5.x release will be made, but if that happens,
it will be a 5.5.x release.  The likelihood of seeing a 5.6 release is
VERY low.

SOLR-2242 is a duplicate of SOLR-6348.  It probably had 4.9 in the fixed
version field because that's what was already in it when it was resolved
as a duplicate.  It's a very old issue that's been around since the 3.x
days.  No changes were committed for SOLR-2242.  The changes for
SOLR-6348 were committed to 5.2 and 6.0.  I have updated the fix
versions in the older issue to match.  The versions should probably all
be removed, but I am not sure what our general rule is for duplicates.

Thanks,
Shawn

The state of Solr 5. Is it in maintenance mode only?

[Jaroslaw Rozanski]

Hi,

Recently I have noticed that couple of Solr issues have been
resolved/added only for Solr 4.x and Solr 6.x branch. For example
https://issues.apache.org/jira/browse/SOLR-2242.

Has Solr 5.x branch been moved to maintenance mode only? The 5 wasn't
around for long before 6 came about so I appreciate its adoption might
not be vast.



-- 
Jaroslaw Rozanski | e: m...@jarekrozanski.com




signature.asc
Description: OpenPGP digital signature