Topic: SME Server 7.0 release status (see thread in SME 7.x forum)

[chris burnat]

Code: [Select]

Is there any info on how to upgrade from 7.0 beta's to the final candidates or later releases? I searched the wiki but could not find anything.


 check: http://forums.contribs.org/index.php?topic=30261.0

[gordonr]

Good Evening,

Ok, I have a question here. I finally visited the sourceforge website and was struck with the impression that SME has kind of splintered. What I mean, and I don't mean to bring up a whole huge issue with it but rather to get clarification, is that it seem that SME is being developed by the sourceforge folks.

The SourceForge folks are the same folks as you'll find over here. We're making use of the best tools we have available. SourceForge provides a solid CVS repository, which allows us to track code changes. We started using the SourceForge bug tracker, but found it to be poor, so we installed Bugzilla here on contribs.org.

The first of my tasks as Development Manager is to unify the 6.0.1/6.5/7.0 streams. The second is to put in place some development tools we can all share. We've done that for 7.0.

Mitel (the Copyright holder for most of the code in the server) has also recently made a decision to use the SourceForge CVS and contribs.org Bugzilla as the central point for all "e-smith" code changes. This is a major step and means we're all working on the same stream.

The next task, after 7.0 is out, is to put time into encouraging contrib developers to check their code into the main repository so we can pull it into a future release. I've already started on that, but it won't get a lot of time until 7.0 goes final.

After being developed, it appears that other folks are distributing it as they see fit. Does this make sense?

I thought that contribs was the sole distributor of the product?

That can never be the case. The Copyright holders (Mitel and  others, including me) have released the code under the GPL. In effect this allows anyone to do almost anything with the code, except claim it as their own. Modifications to the code must also be released for us all to share.

We'd like to encourage everyone to get behind the contribs.org release, and certainly need to remind people of their obligations under the GPL.

I also thought that after the final release of SME 7 came out that it would have the contribs logos on the server manager panels and the likes.


Am I missing the boat somewhere here?

Have a look at 7.0pre1 and the bug tracker. We're most of the way through converting the  server-manager to contribs.org branding. But we're doing so in a way that doesn't cause a fork from the main packages, allowing Mitel and contribs.org to both release versions without requiring a fork (as was done in 6.0.1 and 6.5).

Thanks for raising this - we need to spend a bit of time to clarify that the SourceForge site is used to host various development packages and tools.

[SARK devs]

Problem: SME Banner does not display correctly on the  (7RC1) server-manager screen. This is because the MAS6000 screen uses slightly different stylesheets.

     Fix:-  Correct back to SME colorways. - this is a quick and dirty. A better, release neutral, fix might use the template mechanism to generate the style sheets based upon a DB value (e.g. MAS/SME).

     Modify /etc/e-smith/web/common/css/sme_core.css...

     at line 98.
     Color should be changed from #cccccc to #aec0ec.  

---------->snip

     92 }
     93
     94 /* Core styles for use with sme_header.css*/
     95 body.header {
     96     font-family: Verdana, Arial, Helvetica, sans-serif;
     97     font-size: 11px;
     98     background: #aec0ec;
     99     margin-top: 0px;
    100     margin-right: 0px;
    101     margin-bottom: 0px;
    102     margin-left: 0px;
    103 }

---------->snip

     at line 106.
     Color should be changed to #ffffff.  

---------->snip

    103 }
    104
    105 .hilightbar {
    106     background-color: #ffffff;
    107     font-size: 4px;
    108 }

----------> snip

     at line 113.
     Color should be changed to #809de2.  

----------> snip

    108 }
    109
    110 .infobar {
    111     font-family: Verdana, Arial, Helvetica, sans-serif;
    112     font-size: 11px;
    113     background-color: #809de2;
    114 }

----------> snip


Cheers


Selintra

[gordonr]

Problem: SME Banner does not display correctly on the  (7RC1) server-manager screen. This is because the MAS6000 screen uses slightly different stylesheets.

This is already in the bug tracker:

http://bugs.contribs.org/show_bug.cgi?id=408

Please report *ALL* issues there, and only there. Thanks.

[gordonr]

SME Server 7.0 pre-release 2 is on its way to the mirrors.

If you haven't made the move to 7.0, now is the time.

Please report any issues via the bug tracker, and *only* there, please.

Many thanks to all developers, testers and bug reporters.

In particular, I'd like to thank Gavin Weight for taking on a lot of the small development tasks - thanks Gavin.

Sprechen Sie Deutsch? Wir brauchen Ihren Hilfe! (bug 672)

Gordon


****************************************************************
* IMPORTANT: Pre-upgrade step for 7.0pre1 and 7.0beta releases *
****************************************************************
 Before upgrading to 7.0pre2 from any of the 7.0 test releases,
 you must run the following command:

 kudzu -q

 If you do not do this _prior_ to the upgrade, your system may
 not boot. If this happens, please see the workaround here:

 http://bugs.contribs.org/show_bug.cgi?id=698
***************************************************************

7.0pre1 -> 7.0pre2
===================
- Includes latest CentOS kernel and updates

- Reconfiguration reboot now requested after Software Installer
  updates

- Simple yum wrapper added to remind people to reconfigure after
  using yum

- Completion of change to contribs.org styling

- Updated French translation - thanks Franck Pierre

- Bug fixes - see the bug tracker - Thanks to testers and developers
    See http://bugs.contribs.org/

[wellsi]

SME 7 Pre 2 Changelog and RPM List have been updated in the wiki.

As usual these are available from the Development and Upcoming Releases  pages.

Details on all RPMs in the ISO, including RPM changelog:
http://wellsi.com/sme/info/smebase.php?v=s7p2

Information on all recent releases can be found here.
http://wellsi.com/sme/info/releases.html

[gordonr]

IMPORTANT: Pre-upgrade step for 7.0pre1 and 7.0beta releases

Before upgrading to 7.0pre3 from any of the 7.0 test releases, you must run the following command:

kudzu -q

 If you do not do this prior to the upgrade, your system may not boot. If this happens, please see the workaround here:

http://bugs.contribs.org/show_bug.cgi?id=698

Changelog: 7.0pre2 -> 7.0pre3
- The pre2 image wouldn't boot on some machines (bug 733)
- Bug fixes - see the bug tracker - Thanks to testers and developers. See http://bugs.contribs.org/[/i]

[gordonr]

The SME Server 7 release status is now being tracked in this new thread in the SME Server 7.x forum:

http://forums.contribs.org/index.php?topic=31011.msg129926#msg129926

[dragasoni]

I'm interested in upgrading my server to SME 7.0 from 6.0.  Has anyone sucessfully done this yet?  I don't have a test machine to play with, only my primary server; I depend on this server for email and web, so I can't afford for it to be down.  Should I wait for the final release, or would you all think now is the time?

Thanks in advance!  

-Dragasoni-

[gordonr]

I'm interested in upgrading my server to SME 7.0 from 6.0.  Has anyone sucessfully done this yet?  

Yes, many. It is painless for an unmodified server and painless for many of the common contribs.

I don't have a test machine to play with, only my primary server; I depend on this server for email and web, so I can't afford for it to be down.  Should I wait for the final release, or would you all think now is the time?

Now is the time. If you wait until the final release and have a problem, it will be too late to fix it.

[dragasoni]

Ok, just download the latest ISO, burn to CD, and run the upgrade, correct?  If I have a problem, I can post on Bugzilla, and the problem will be taken care of?

Thanks again for your time, I really appreciate it.

-Dragasoni-[/quote]

[gordonr]

Ok, just download the latest ISO, burn to CD, and run the upgrade, correct?  

Correct.

If I have a problem, I can post on Bugzilla, and the problem will be taken care of?

Yes, please post any issues to Bugzilla. Whether, and how quickly, it will be taken care of depends on the availability of people to look at it.

[brianr]

hey slow down here!!

you must at least be sure you have a full backup of the data before you do the upgrade, either a tape backup or just copy the disc contents to another disc.  

If you are using the software raid function, then you could do the upgrade only on one of the hard drives, leave the other disconnected until you are sure that the data has survived the upgrade.

[gordonr]

you must at least be sure you have a full backup of the data before you do the upgrade, either a tape backup or just copy the disc contents to another disc.  

Of course. But that should be true of any upgrade, no matter how minor.

If you are using the software raid function, then you could do the upgrade only on one of the hard drives, leave the other disconnected until you are sure that the data has survived the upgrade.

Careful here:

http://bugs.contribs.org/show_bug.cgi?id=961

Could we stop using this thread and move to the 7.x category please?