Topic: SME 6 Release

[James Phillips]

Hi,

I don't mind to be rude anyone, but do you know how many beta's are left before the release of SME 6 or can anyone give an approx date?

Thanks,
James Phillips

[Deunan Knute]

Well..

As long as it takes..  and it will be released when it is done..

Not much of an answer isn't it?  That's the answer anyone gets for the question in question  


Regards

Deunan Knute
---
ASCII funny question, get funny ANSI

[Greg Zartman]

> I don't mind to be rude anyone, but do you know how many
> beta's are left before the release of SME 6 or can anyone
> give an approx date?

SME 6 commercial version has been released, several weeks ago.   It's the developer version that remains in beta.  If you really think about it, it makes sense that the developer version remains beta.   The name "developer version" implies that it is a test bed.   I have no idea what Mitel's intentions are with the developer version, but I can't seen any incentive for them to create an "offical" unsupported final release of SME 6.    IMO, keeping it beta allows them to continually test new packages for their commercial version while providing all of us with a free OS.

Greg Zartman

[HArdijs]

>IMO, keeping it beta allows them to continually test new packages for their commercial version
>while providing all of us with a free OS.

So - then the question is - is the 6b3 version sufficiently final?

[Martin Trigg]

I am no expert so can't say how suitable 6.0b3 is for production use but when reading through Mitels "Security Advisory - Potential ProFTPD Vulnerability" I noted the following in regards to users of V5.5 or below:

Users of those obsolete versions should:
     - disable FTP access until an upgrade can be performed
     - upgrade to either 5.6 or 6.0beta3 and apply the update for that version

I might be reading too much into it, but does this imply that 6.0b3 is suitable for production environments where 5.6 has been used?

Martin

[Greg Zartman]

> I might be reading too much into it, but does this imply that
> 6.0b3 is suitable for production environments where 5.6 has
> been used?

I'd run 6.0b3 with updates applied in a production environment.  I'm running SME 6 Servicelink and can't see a difference between my production Servicelink box and my testbox running SME 6b3 with updates.

Greg Zartman

[Guck Puppy]

Greg Zartman wrote:

> I'd run 6.0b3 with updates applied in a production
> environment.  I'm running SME 6 Servicelink and can't see a
> difference between my production Servicelink box and my
> testbox running SME 6b3 with updates.

What about the difference between 5.6 and 6.0? That's what I'm most interested in on a day to day basis...

G

[Greg Zartman]

> What about the difference between 5.6 and 6.0? That's what
> I'm most interested in on a day to day basis...

Lots:
http://www.e-smith.org/article.php3

I'd recommend the upgrade.

Greg Zartman

[Jim Danvers]

Hi guys....

Guess I'm kind of late to the party (what else is new?)...    Question regarding this present 6.xBeta release and to some extent I suppose, the final non-beta 6.0, when it gets released:

What about existing 5.6 servers (like mine) that have tons of e-mail on them, and some ibays cfg'd?  Can I just do a backup to desktop and expect that a restore back to a 6.x (latest & greatest present beta or later) to work?  Sorry if this is a lamo question...  I haven't realy been following these threads - have sort of been holding off until I see/read from the main site "Announcing SME Server 6.0 unsupported developer release" has been released.  Note the lack of the word "beta"....

Now, Greg's comment and link he provided has my interest....    I am perfectly happy with my little server @present though - I would hate for anything 'bad' to happen....  ;(  lol!!

TIA...

-=- jd -=-

[Michael Soulier]

Jim Danvers wrote:
>
> What about existing 5.6 servers (like mine) that have tons of
> e-mail on them, and some ibays cfg'd?  Can I just do a backup
> to desktop and expect that a restore back to a 6.x (latest &
> greatest present beta or later) to work?

Yes. Better yet, pop in the CD and choose the upgrade option. When you're done, make sure you apply all update rpms.

Mike

[Greg Zartman]

> Yes. Better yet, pop in the CD and choose the upgrade option.
> When you're done, make sure you apply all update rpms.

I'll even do you one better.  I created a script to automatically update SME6b3 with all update rpms.

1. Terminal into your server as root.

2. wget http://www.leiinc.com/repository/Linux/Mitel_SME_Server/Updates/SME6b3/update.pl

3. perl update.pl

That's it.

Regards,

Greg Zartman

[Jim Danvers]

Greg...

I finally got around to installing it (6.0b3) on another machine that I have here for testing (I chickened out and didn't want to mess w/my live one just yet....  )  So anyway - I installed from scratch, used wget and got you're perl script and ran it - nice!    I'm glad that I read through/looked at it first though as I noticed that you (probably a good idea too) commented out the last two lines regarding the signal upgrade thing and the signal reboot.  I manually ran those two parts...  I just cut -n- pasted 'em out of the script while in an ssh session using putty.

Anyway - cool beans.  Thanks!

-=- jd -=-

[Stewart]

> It's the developer version that remains in beta. If you really think about it,
> it makes sense that the developer version remains beta. The name
> "developer version" implies that it is a test bed.

Except that the older policy and one that other companies have followed is
that you would add a .1 to your "developer version" so that outside developers
know that the commercial version is shipping.

One understands that SME 6 has moved well beyond a sourceforge project,
but I suspect that many of the improvements from v3 to v5 have come from
outside sources.

Hopefully the chance to add Modules to SME 7 will stiil be there.

[Charlie Brady]

Stewart wrote:

> One understands that SME 6 has moved well beyond a
> sourceforge project,

SME never was a sourceforge project.

> but I suspect that many of the improvements from v3 to v5
> have come from outside sources.

The RedHat packages obviously have; the e-smith-* changes with very few exceptions have not. See the package changelogs for details.

Charlie