Publish upgrade tutorial for iRedMail-0.9.4.
This commit is contained in:
parent
92d23794b3
commit
aba3d46616
|
@ -2,12 +2,12 @@
|
|||
|
||||
[TOC]
|
||||
|
||||
__WARNING: THIS IS STILL A DRAFT DOCUMENT, PLEASE DO NOT APPLY IT.__
|
||||
|
||||
## ChangeLog
|
||||
|
||||
> We offer remote upgrade service, check [the price](../support.html) and [contact us](../contact.html).
|
||||
|
||||
* 2016-01-25: Initial publish.
|
||||
|
||||
## General (All backends should apply these steps)
|
||||
|
||||
### Update `/etc/iredmail-release` with new iRedMail version number
|
||||
|
@ -22,7 +22,7 @@ so that you can know which version of iRedMail you're running. For example:
|
|||
0.9.4
|
||||
```
|
||||
|
||||
### Upgrade iRedAPD (Postfix policy server) to the latest 1.7.1
|
||||
### Upgrade iRedAPD (Postfix policy server) to the latest 1.8.0
|
||||
|
||||
Please follow below tutorial to upgrade iRedAPD to the latest stable release:
|
||||
[Upgrade iRedAPD to the latest stable release](./upgrade.iredapd.html)
|
||||
|
|
|
@ -17,7 +17,7 @@
|
|||
<li><a href="#changelog">ChangeLog</a></li>
|
||||
<li><a href="#general-all-backends-should-apply-these-steps">General (All backends should apply these steps)</a><ul>
|
||||
<li><a href="#update-etciredmail-release-with-new-iredmail-version-number">Update /etc/iredmail-release with new iRedMail version number</a></li>
|
||||
<li><a href="#upgrade-iredapd-postfix-policy-server-to-the-latest-171">Upgrade iRedAPD (Postfix policy server) to the latest 1.7.1</a></li>
|
||||
<li><a href="#upgrade-iredapd-postfix-policy-server-to-the-latest-180">Upgrade iRedAPD (Postfix policy server) to the latest 1.8.0</a></li>
|
||||
<li><a href="#upgrade-iredadmin-open-source-edition-to-the-latest-stable-release">Upgrade iRedAdmin (open source edition) to the latest stable release</a></li>
|
||||
<li><a href="#upgrade-roundcube-webmail-to-the-latest-stable-release">Upgrade Roundcube webmail to the latest stable release</a></li>
|
||||
<li><a href="#fixed-no-daily-cron-job-to-backup-sqlldap-database">Fixed: No daily cron job to backup SQL/LDAP database</a></li>
|
||||
|
@ -29,11 +29,13 @@
|
|||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<p><strong>WARNING: THIS IS STILL A DRAFT DOCUMENT, PLEASE DO NOT APPLY IT.</strong></p>
|
||||
<h2 id="changelog">ChangeLog</h2>
|
||||
<blockquote>
|
||||
<p>We offer remote upgrade service, check <a href="../support.html">the price</a> and <a href="../contact.html">contact us</a>.</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>2016-01-25: Initial publish.</li>
|
||||
</ul>
|
||||
<h2 id="general-all-backends-should-apply-these-steps">General (All backends should apply these steps)</h2>
|
||||
<h3 id="update-etciredmail-release-with-new-iredmail-version-number">Update <code>/etc/iredmail-release</code> with new iRedMail version number</h3>
|
||||
<p>iRedMail stores the release version in <code>/etc/iredmail-release</code> after
|
||||
|
@ -44,7 +46,7 @@ so that you can know which version of iRedMail you're running. For example:</p>
|
|||
0.9.4
|
||||
</code></pre>
|
||||
|
||||
<h3 id="upgrade-iredapd-postfix-policy-server-to-the-latest-171">Upgrade iRedAPD (Postfix policy server) to the latest 1.7.1</h3>
|
||||
<h3 id="upgrade-iredapd-postfix-policy-server-to-the-latest-180">Upgrade iRedAPD (Postfix policy server) to the latest 1.8.0</h3>
|
||||
<p>Please follow below tutorial to upgrade iRedAPD to the latest stable release:
|
||||
<a href="./upgrade.iredapd.html">Upgrade iRedAPD to the latest stable release</a></p>
|
||||
<p>Detailed release notes are available <a href="./iredapd.releases.html">here</a>.</p>
|
||||
|
|
Loading…
Reference in New Issue