I started to reply to this last night...
There is not “stay with the latest git policy” ... It has long been stated you need to test for your actual deployment make sure it works for you then deploy.
On the “are you running the latest git?” thing. The FreeSWITCH Dev Team is pretty small and pretty much everyone on the dev team has another ‘day job’. so them asking can you duplicate the issue on the latest git is a way to reduce the amount of bug finding by asking the reporter to help the dev team. Even better is if you can help identify a previous working version in git and the commit at which it stopped working that’s even better (see git bisect for helping out on this)
L
On 1/11/12 8:23 AM, "Anita Hall" <anita.hall@simmortel.com> wrote:
Some release policy along the lines of Ubuntu LTS will be great!
Our client has been running FS for more than 2 years now and they do not have a "stay with the latest git" policy. That would be a pain anyway. They are currently doing around 80 E1 lines at 10 different locations.
@MC, eagerly awaited :)
regards,
Anita
On Wed, Jan 11, 2012 at 7:42 PM, Saugort Dario Garcia Tovar <dgarcia@anew.com.ve> wrote:
Hi all,
About a strategy to release and support.
I work for a integrator. We have in our portafolio two big brand: Alcatel and Genesys. They give new minor releases and hotfixes almost every week in their products. Mayor releases are available in one year, sometimes more.
About minor releases and hot-fixes, it depend on our local scenario. Not all our customer has issues than involves/require apply hot-fixes each week. We use this approach:
1. If there is an issue, we look in there are an aplicable hotfix. If not, we try to find a workaround or get a estimated date for a hotfix.
2. Each year we offer to our customer access to last binaries to upgrade their platform to the latest release
Also, you have to "design" an integral political procedure for upgrades, hot-fixes and roll-back. Because, FS depend on OS, and other components like mediagateway, routers, etc. I have seen in our customer, when they apply a patch in the OS or their pbx, could affect other systems.
On 1/10/2012 11:46 PM, Michael Collins wrote:
Enterprise can't afford patch& upgrade daily. You guys need to take a strategy to release and support. For instance, two release: stable release will has a life span 3 years and be supported. Test release with latest features.
We've got some things in the works. Stay tuned!
-MC
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
No virus found in this message.
Checked by AVG - www.avg.com <http://www.avg.com>
Version: 2012.0.1901 / Virus Database: 2109/4734 - Release Date: 01/10/12