Summary:	ASTERISK-01418: [request] backports for 1.0-stable
Reporter:	zoa (zoa)	Labels:
Date Opened:	2004-04-16 03:25:25	Date Closed:	2011-06-07 14:04:39
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	What do you guys think is already in -head and should be backported to -stable, and already looks STABLE & mature. Personally, I think all timestamp related fixes seem fixed at this time, the ulaw to alaw clicks and cisco jitter being the last ones, not having this in the stable means its difficult to mix -stable and -head in production systems and carriers and clients should all use the same branch. Whats your opinion on this, and what else do you think should absolutely make it to -stable ?
Comments:	By: linuss (linuss) 2004-04-16 05:47:42 Me too! For those of us using these in production grade environments these fixes are very important. By: geertn (geertn) 2004-04-16 12:32:52 I think all rtp.c fixes should be backported. By: rthrash (rthrash) 2004-04-28 14:55:40 advanced voicemail features By: vaewyn (vaewyn) 2004-04-30 08:51:06 (If accepted) HasVoicemail patch in bug 1520. Then if it is decided to begin deprecating HasNewVoicemail people that decide on 1.0 will have HasVoicemail for use and we don't have to make exceptions in the documentation. Patch is trivial and will not affect stability in the least. By: Brian West (bkw918) 2004-04-30 11:01:21 stable WILL not get any new features or apps.  I don't think the timestamp stuff will be back ported either.  We are going to release 1.0 and 1.1 at the same time so whats the point.  1.0 will be the time tested mother approved version while 1.1 will be the stable featureful release. Thats the plan as I was told. By: Brian West (bkw918) 2004-04-30 11:02:44 Zoa talk to mark about the alaw to ulaw clicks but the rest is pretty much not going to make it back to stable as it touches too much of th ecore of asterisk.