[Freeswitch-dev] is there any info abount which git tag/ Freeswitch release is stable?

Michael Collins msc at freeswitch.org
Thu May 12 19:35:11 MSD 2011


On Thu, May 12, 2011 at 1:02 AM, Tom Parrott <tomp at tomp.co.uk> wrote:

> Hi,
>
> Does the file at http://latest.freeswitch.org change each day to represent
> the current state of HEAD?
>
Correct.
-MC


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


More information about the FreeSWITCH-dev mailing list