And for new installs on 4.6, should we yum update daily as new packages are
being compiled on a daily basis?

-
MM


On Wed, Nov 14, 2012 at 10:57 AM, Douglas Hubler <[email protected]> wrote:

> short answer...
> not officially released
>
> long answer...
> 4.6 is not officially released even though i believe it to be more
> stable than 4.4.  Users that have run into issues with 4.6 may
> disagree, because some are finding some issues due to the sheer amount
> of changes that went into 4.6   Unfortunately we're finding issues
> very slowly hence the delay.
>
> ezuce has been using 4.6 build for quite some time so if you're doing
> new installs, without question go with 4.6.
>
> The other day the 4.6 release was horribly broken but it was found and
> fix immediately.  We have automated tests, but it still requires a
> little manual intervention to start and run
>
>
> On Wed, Nov 14, 2012 at 1:26 PM, Claas Hilbrecht
> <[email protected]> wrote:
> > Hello Jesse,
> >
> >>  I tried searching before asking, however, I could find the answer. Is
> > [...]
> >> library still shows that 4.4 is stable and 4.6 is beta. Is that
> accurate?
> >
> > I've asked a similar question at 07. Nov. 2012 with the title: "wiki (and
> > other sites) outdated?" on this list. The answer was something like: "the
> > wiki and download pages are community driven, so that's why there are not
> > up to date".
> >
> > As far as I understand sipXecs 4.6 is released. Just the information is
> not
> > up to date.
> >
> > --
> >  Claas Hilbrecht
> >  http://www.jucs-kramkiste.de
> >
> > _______________________________________________
> > sipx-users mailing list
> > [email protected]
> > List Archive: http://list.sipfoundry.org/archive/sipx-users/
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to