Release Strategy

The B1 Usability Package release strategy is running on a yearly schedule with a major release every January.

The yearly schedule

During a year there are 10 B1 Usability Releases:

• January release (Major release)
• February (Incremental release)
• March (Incremental release)
• April (Minor release)
• May (Incremental release)
• June (Incremental release)
• July (No release due to summer vacations)
• August (Minor release)
• September (Incremental release)
• October (Incremental release)
• November (Minor release)
• December (No release due to planning of next major release)

B1 Usability and supported versions

When a major released is first released it is generally supported for 2 years. 

Example:

• - When B1UP 4.x is released all B1UP 4.x and 3.x are supported and maintained while 2.x is not supported anymore
  • 4.x will have the 10 yearly releases.
  • 3.x is in maintenance mode and patches is released as needed to fix issues (if any) but no new major features are added.
• When B1UP 5.x is released all B1UP 5.x and 4.x are supported and maintained while 3.x is not supported anymore
  • 5.x will have the 10 yearly releases.
  • 4.x is in maintenance mode and patches is released as needed to fix issues (if any) but no new major features are added.

SAP Business One RampUp and Beta versions

During a SBO RampUp, depending on the SBO-client changes, a Beta version of the B1 Usability Package might be needed. When the rampup is released the B1UP Team will through tests determine if a Beta is needed or the current version can act as the beta.

NB: A BETA VERSION WILL ALWAYS BE RECOGNIZED BY THE WORD BETA IN THE DOWNLOADED FILENAME 

NB: PEOPLE USING BETA VERSIONS OF B1UP MIGHT NEED UNINSTALL AND ADDITIONAL TWEAKS WHEN THE FINAL VERSION IS RELEASED, COMPARE TO NORMAL UPGRADES.

B1UP version vs. SAP Business one version

• B1UP 1.x = SBO2004
• B1UP 2.x = SBO2005
• B1UP 3.x = SBO2005 / SBO2007 (Also compatible with SBO 8.8)
• B1UP 4.x = SBO 8.8 / 8.81 / 8.82
• B1UP 5.x = SBO 8.81 / 8.82

Version numbering

The way we version the releases happen with 4 numbers

<Major>.<Minor>.<Incremental>.<Hotfix>

Example:

4.2.1.0

Major release number

This number is the main version number of the B1 Usability Package. B1UP follows a yearly cycle so this number is increased once per year in January.

Major versions of B1UP will mostly contain changes to core product code to deal with B1UP structural changes (Examples: .Net Framework version change and the a new license system).

The B1UP Team will always try to make the transition between major versions as smooth as possible, but you should be aware that smaller tweaks might be needed.

Minor release number

A minor release of the B1UP happens quarterly. Minor releases focus mainly on enhancing the existing functionality with new features and new modules.

Incremental release number

This number is the release number that normally will change for new release and symbolize the planned monthly update. Such a build normally consists of bug-fixes and minor new functionality to the existing modules of the add-on, but not new modules).

Incremental builds are planned to be released at the end of each month of the year (except July and December).

Hotfix/Special Build Number

The final digit in the version number will in scheduled releases always be 0 but is used for 3 purposes:

• Should the unfortunate event happen in a scheduled release, a critical error is found; a hot fix build will be issued. Such a built will not end on 0 but 1, 2, 3 and so on if needed.
• During beta releases the number will be used.
• In a maintenance release this number is increased every time an as needed release comes out

Release_Strategy.pdf