You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Curtis Wensley edited this page Nov 19, 2015
·
3 revisions
Eto.Forms uses the following versioning scheme:
The master branch is the stable/release branch.
The develop branch is used for ongoing development, merging, etc.
The develop branch uses an auto generated build/revision based off the build date/time.
v2.0 stable, 2.1 in development
Branch
Version
File Version
Informational/Nuget
master-2.0
2.0.0.0
2.0.0.0
2.0.0
develop-2.1
2.0.*
2.0.*
2.1.0-build{build}
v2.1 stable, 2.2 in development
Branch
Version
File Version
Informational/Nuget
master-2.1
2.1.0.0
2.1.0.0
2.1.0
develop-2.2
2.1.*
2.1.*
2.2.0-build{build}
Patches
Patches will be based off the master branch and increment the nuget patch number and file version, but retain the same assembly version. This allows for strong naming compatible assemblies. For example, a new patch to 2.0 would result in: