cancel
Showing results for 
Search instead for 
Did you mean: 

What exactly is the difference between the SPXX and the SPXXX series?

Former Member
0 Kudos
EBF 21517: 15.7 SP102 - 64 Bit 15.726 Jul 2013EBF/Patch






EBF 21202: 15.7 SP50 - 64 Bit 15.723 Jul 2013EBF/Patch

Why is there are SPXX (5x and soon 6x) and a SPXXX (10x) series of ebfs?  There doesn't seem to be a clear indication.  I'm leaning towards the idea of whomever thought that numbering scheme up was up to something devious

Accepted Solutions (1)

Accepted Solutions (1)

sap_mk
Active Participant
0 Kudos

Hi Jason,

Sorry, nothing devious to the numbering sheme. The SPxxx series came first while we still had ESD4.x going. Some people were confused about whether or not you would apply ESD4.x over SPxxx. We thought it would be easier to understand if we used lower numbers. Since SP1xx was already available, we went with SP50 and eventually SP60.

I explain SP1xx as a new release with new features. Think of SP100 kind of like 15.8 and SP1xx as ESDs off 15.8. You wouldn't apply 15.7 ESD4.x to a 15.8 ESDx server. I hope that makes it easier to understand.

Mark

Former Member
0 Kudos

Not really.

SP50 (soon SP60) is an ebf off of 15.7 esd 4.  SP100/102 is for a 15.8 like animal.  Why are SP100/102 listed as 15.7 SP100/102 instead of 15.8 sp10x? 

From the customer perspective SP10x is newer than SP50 but wait, the release is only 3 days apart.  Which one do I install?  and so on.  The numbering scheme should have said something like "15.7 esd 4 SP50"  and "15.8 sp100" so there is a clear distinction between the two. SP numbers should always increment and not jump around imo

sap_mk
Active Participant
0 Kudos

SP1xx is not 15.8. There is no 15.8. I only suggested that as a way to think of SP1xx. They are all 15.7 releases because if we call it 15.8 that has other EOL timeline implications.

SP1xx has new features that won't be in the SPxx releases. If you are on 15.7 ESDx and you want new features, move to 15.7 SP1xx. If you only want bug fixes, use 15.7 SP50 (and later SP60).

Former Member
0 Kudos

So basically, SP50 is a complete waste of engineering resources.  Good to know.

sap_mk
Active Participant
0 Kudos

Not sure why you would say that. It is no different than years ago when we had multiple codelines active. Not everyone is in a hurry to upgrade to new features. Some just need bug fixes on their existing codeline. SP50 satisfies that need without going through all the testing required for a release with a bunch of new features (SP1xx).

Answers (1)

Answers (1)

Former Member
0 Kudos

Release vversion numbers of SP50 and SP10x are really confusing.