<HTML>
<HEAD>
<TITLE>How Patches to the code base work</TITLE>
</HEAD>
<BODY>
<FONT FACE="Monaco, Courier New"><SPAN STYLE='font-size:11pt'>Hey Guys,<BR>
<BR>
Tony & Crew have been hot and heavy fixing bugs and coming up with new ways to make FreeSWITCH better.<BR>
<BR>
Now during the cycle, we get bugs reported on the stable branch, which in almost all cases are also bugs on the Development branch (or also possible not a bug on the dev branch as it was fixed there since the release was cut).<BR>
<BR>
So lets say you have just reported a bug, and one of the developers fixes it, 99.999% of the time, that bug would have been resolved in the git master branch aka HEAD. When this happens the patch does not immediately go into the stable branch. We wont put untested code there unless there is a VERY VERY compelling reason to do so like security issue... Those patches will work their way in as the release cycle progresses...<BR>
<BR>
If Tony & Crew patch an issue and ask you to test it, they arent asking you to test it on stable they are asking you to test it in head... From there, we can evaluate if the patch goes into stable sooner then later... <BR>
<BR>
As with any software, patching to fix one issue can introduce another issue. This happens to all programmers, some more then others. Sometimes its not so bad, other times, its horrific. (I’ve even seen core FS Devs commit code that leaves the build broken.) No one does this sort of stuff on purpose but it does happen, that’s why we ask for everyone to test master (HEAD) for new patches. We would hate to break the stable because we dropped untested code directly in there.<BR>
<BR>
K<BR>
<BR>
<BR>
-- <BR>
Ken<BR>
<FONT COLOR="#0000FF"><U><a href="http://www.FreeSWITCH.org">http://www.FreeSWITCH.org</a><BR>
<a href="http://www.ClueCon.com">http://www.ClueCon.com</a><BR>
<a href="http://www.OSTAG.org">http://www.OSTAG.org</a><BR>
</U></FONT>irc.freenode.net #freeswitch<BR>
</SPAN></FONT>
</BODY>
</HTML>