forked from EasyNetQ/EasyNetQ
-
Notifications
You must be signed in to change notification settings - Fork 0
A Note on Versioning
Mike Hadlow edited this page Dec 11, 2013
·
4 revisions
EasyNetQ is alpha software. It is under heavy development with frequent changes both to the internals and to the public API. The developers follow the following versioning scheme:
<major>.<minor>.<patch>.<build-number>
So for example, the version at the time this was written was:
0.25.2.174
We use the following, somewhat semantic, versioning policy:
major - 0 to indicate that this is alpha software.
minor - increments when there is a breaking change to the API.
patch - indicates a bug fix or some internal change.
build-number - increments on each build on the CI server.
We use the code better (http://teamcity.codebetter.com/) CI server for our builds. Each change in the master repository triggers a build. Each is build is automatically published to NuGet.
There is no development version, or stabilization process, so you should regression test your software when upgrading your NuGet EasyNetQ package.
- Quick Start
- Introduction
- A Note on Versioning
- Installing EasyNetQ
- Connecting to RabbitMQ
- Logging
- Publish
- Subscribe
- Request Response
- Send Receive
- Topic Based Routing
- Polymorphic Publish and Subscribe
- Publisher Confirms
- Scheduling Events with Future Publish
- Auto Subscriber
- Non Generic Publish & Subscription Extension Methods
- Error Conditions
- Re Submitting Error Messages With EasyNetQ.Hosepipe
- The Advanced API
- Cluster Support
- Wiring up EasyNetQ with TopShelf and Windsor
- Replacing EasyNetQ Components
- Using Alternative DI Containers