SIPServer should be packaged into releases
Bug #1083290 reported by
Chris Sharp
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SIPServer |
New
|
Undecided
|
Unassigned |
Bug Description
For organizations who rely on packaged Evergreen releases, we need a way to know whether a particular version of the SIPServer would be compatible with a particular version of Evergreen. We also receive multiple requests from vendors regarding which features are present in the SIPServer at a given point in time. Packaging the SIPServer into numbered releases would greatly ease the uncertainty around this.
To post a comment you must log in.
Chris makes a valid suggestion, but I disagree with it for a couple of reasons.
1. The SIPServer code is written in such a way that it remains compatible with a broad range of Evergreen releases. It typically checks the Evergreen capabilities before reporting/using the backend capabilities.
2. Changes to add new functionality to SIPServer more often than not end up requiring more changes to the Evergreen code than to the SIPServer code. In some cases, the functionality only need be added to Evergreen and SIPServer picks it up automatically.
I am not necessarily against doing SIPServer releases, but listing which versions of Evergreen a given SIPServer release is compatible with is a bit dicey. In principal, it is compatible with all releases of Evergreen. Some features will or won't be available depending on the Evergreen version. I think the latter is better documented in Evergreen with a note there if it also requires upgrading the SIPServer software to get the feature.