<br><br><div class="gmail_quote">On Thu, May 12, 2011 at 1:02 AM, Tom Parrott <span dir="ltr"><<a href="mailto:tomp@tomp.co.uk">tomp@tomp.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<br>
Does the file at <a href="http://latest.freeswitch.org" target="_blank">http://latest.freeswitch.org</a> change each day to represent<br>
the current state of HEAD?<br></blockquote><div>Correct.</div><div>-MC</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
If so I could version that as 1.0.7-yyyymmdd to make it more suitable for<br>
RPMs.<br>
<br>
Thanks<br>
<font color="#888888">Tom<br>
</font><div><div></div><div class="h5"><br>
>><br>
>> I believe the developers have been discussing making a 1.0 stable branch<br>
>> soon with only bugfix and stability improvements and moving new<br>
>> development<br>
>> onto a new 1.2 branch. If that happens then perhaps you'll be more<br>
>> comfortable with that branch. Not sure when that's planned for though.<br>
><br>
><br>
> The issue by the way is with developers. While there's a lot of developers<br>
> and plenty of people using FS in the wild testing and making bug reports<br>
> on<br>
> Jira and plenty of people volunteering support on the list and IRC,<br>
> something like 90% of the code is still written by half a dozen people.<br>
> It's<br>
> damn good code though. :) That's too much to make it easy for them to both<br>
> maintain a stable branch and work on the newer branch, so up to this point<br>
> it has been better to focus on making FS complete, feature rich and stable<br>
> all in the same branch. Once the branches diverge, someone is going to<br>
> have<br>
> to both handle bug reports for 2 different codebases and also look at all<br>
> 1.2 changes to decide whether any are work backporting to 1.0 which won't<br>
> always be trivial if the code diverges significantly.<br>
><br>
> -Steve<br>
><br>
><br>
> On 12 May 2011 08:45, Steven Ayre <<a href="mailto:steveayre@gmail.com">steveayre@gmail.com</a>> wrote:<br>
><br>
>> The 1.07 version available at <a href="http://latest.freeswitch.org" target="_blank">http://latest.freeswitch.org</a> seems to be<br>
>> rebuilt<br>
>>> each night, does this mean that a 1.07 built yesterday is different<br>
>>> from<br>
>>> one built today?<br>
>><br>
>><br>
>> Yes. Think of it as a release candidate for 1.0.8<br>
>><br>
>> The git head is pretty much the most stable. Development tends to move<br>
>> too<br>
>> fast to make more regular 'stable' releases. You should of course test<br>
>> releases work as expected before putting them into production.<br>
>><br>
>> If you find a Git version that you're comfortable with, then you can<br>
>> roll<br>
>> out that version across your whole network even if there's a newer Git<br>
>> head<br>
>> by running:<br>
>> > git clone git://<a href="http://git.freeswitch.org/freeswitch.git" target="_blank">git.freeswitch.org/freeswitch.git</a><br>
>> > cd freeswitch.git<br>
>> > git checkout GIT_HASH<br>
>><br>
>> I believe the developers have been discussing making a 1.0 stable branch<br>
>> soon with only bugfix and stability improvements and moving new<br>
>> development<br>
>> onto a new 1.2 branch. If that happens then perhaps you'll be more<br>
>> comfortable with that branch. Not sure when that's planned for though.<br>
>><br>
>> -Steve<br>
>><br>
>><br>
>> On 10 May 2011 19:39, Tom Parrott <<a href="mailto:tomp@tomp.co.uk">tomp@tomp.co.uk</a>> wrote:<br>
>><br>
>>> Hi,<br>
>>><br>
>>> I work for a company selling call tracking services, and we have<br>
>>> recently put into production a 3 node Freeswitch cluster to use<br>
>>> features<br>
>>> such as call recording and call announce.<br>
>>><br>
>>> We are using the event socket feature to control freeswitch from our<br>
>>> custom written service.<br>
>>><br>
>>> I have found Freeswitch a pleasure to use, and much easier to get along<br>
>>> with than Asterisk.<br>
>>><br>
>>> However one thing that has concerned me is the lack of regular<br>
>>> point-in-time releases.<br>
>>><br>
>>> When putting services in production, we use RPMs to allow us to easily<br>
>>> upgrade (and if need be rollback) software versions.<br>
>>><br>
>>> The 1.07 version available at <a href="http://latest.freeswitch.org" target="_blank">http://latest.freeswitch.org</a> seems to be<br>
>>> rebuilt each night, does this mean that a 1.07 built yesterday is<br>
>>> different from one built today?<br>
>>><br>
>>> If I can offer any assistance with the automation of point-in-time<br>
>>> tagged releases I would be happy to help, as I feel this would make<br>
>>> Freeswitch more attractive to commercial operations as it would easily<br>
>>> fit into well defined release processes.<br>
>>><br>
>>> Thanks<br>
>>> Tom<br>
>>><br>
>>> _______________________________________________<br>
>>> FreeSWITCH-dev mailing list<br>
>>> <a href="mailto:FreeSWITCH-dev@lists.freeswitch.org">FreeSWITCH-dev@lists.freeswitch.org</a><br>
>>> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev</a><br>
>>> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-dev</a><br>
>>> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
>>><br>
>><br>
>><br>
><br>
<br>
<br>
<br>
_______________________________________________<br>
FreeSWITCH-dev mailing list<br>
<a href="mailto:FreeSWITCH-dev@lists.freeswitch.org">FreeSWITCH-dev@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-dev</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br>