5,576
edits
Changes
From SME Server
Jump to navigationJump to search→Preparation for a new ISO release
====The Smeserver version name====
====The Smeserver version name====
The Version number comes from a rpm, smeserver-release, you need to bump the version in the spec file and build the rpm, think to push it to smeupdates-testing.
The Version number comes from a rpm, smeserver-release, you need to bump the version in the spec file and build the rpm, think to push it to smeupdates-testing.
====RPM dependencies====
====RPM dependencies====
The smeos, smeupdates, and smeupdates-testing repos are included so we can stage the packages we are going to release without actually having to release them. Normally the smeupdates-testing repo is used for verification (testing is for developer testing).
The smeos, smeupdates, and smeupdates-testing repos are included so we can stage the packages we are going to release without actually having to release them. Normally the smeupdates-testing repo is used for verification (testing is for developer testing).
* Every package that needs to be in the ISO will go into smeos, '''by the buildsys.'''
* Every package that needs to be in the ISO will go into smeos, '''by the buildsys.'''
* Packages that are needed for building the ISO, but not actually needed in the ISO, will be in smeextras
* Packages that are needed for building the ISO, but not actually needed in the ISO, will be in smeextras
=====How get a Fully updated ISO=====
If your Iso is not fully updated and a 'yum update' fetch updates after the first boot, in generally centos updates. You will need to push missed updates from smetest to smeupdates-testing.
====RPM QA verification====
====RPM QA verification====
{{Warning box|'''During the ISO release schedule, ALL RPMS MUST BE VERIFIED IN SMEUPDATES-TESTING.'''}}
{{Warning box|'''During the ISO release schedule, ALL RPMS MUST BE VERIFIED IN SMEUPDATES-TESTING.'''}}
====Server-Manager translations====
====Server-Manager translations====
