[OpenSIPS-Users] [RFC] New Release Policy for OpenSIPS project
brett at nemeroff.com
Sun Nov 25 16:32:10 CET 2012
On Thu, Nov 22, 2012 at 4:34 AM, Bogdan-Andrei Iancu <bogdan at opensips.org>wrote:
> Release cycles
> - instead of a feature driven release cycle, I would prefer a time
> driven release cycle - because it is more predictable and being feature
> driven may actually escalate the time to the next release (the snowball
> effect) - see the timing for 1.7, 1.8 versions
> - have a 5-7 months release cycle (depending on the required volume of
> - smaller steps in releases will be more friendly to users as there
> are no big gaps between releases, easier and more appealing to upgrade ;
> also shorter release cycles will make new features available in stable
> versions much faster.
Just my two cents here...
With regards to the release cycle... I typically find myself doing
"production" deployments for my clients. What I need is a stable version.
And then hotfixes as bugs are discovered.
I prefer feature driven releases because I can look forward to when feature
X will be available. My production deployments typically run untouched
while in production mode. Upgrades occur when new features are needed AND
available in stable builds. I don't typically upgrade simply because an
upgrade is available. Of course, I'll normally upgrade for critical fixes
or security fixes (which I'd see as a hotfix typically and not a full
If I knew a release was going to be available on a particular date, I would
without question start reviewing that release and it's new capabilities;
but I wouldn't need it for a production build.
If I knew a feature was available on a certain date, I could pitch that to
my clients if it was a feature they might need. Also, I'm afraid that time
based releases may rush features out before they are ready.
That's just my perspective based on my workflow. I'm sure there are others
that feel differently. :)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users