[OpenSIPS-Users] [RFC] New Release Policy for OpenSIPS project

Jeff Pyle jpyle at fidelityvoice.com
Mon Nov 26 15:02:37 CET 2012


On Sun, Nov 25, 2012 at 10:32 AM, Brett Nemeroff <brett at nemeroff.com> wrote:

>
>  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 release)
>
> 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. :)
> -Brett
>


I, for one, share Brett's perspective.


- Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20121126/53286ae5/attachment.htm>


More information about the Users mailing list