What happens when a component gets a new version? (e.g. Dovecot already has a new version v1.1.18 that isn't part of 0.5.0rc2 ) Are you tied to the iredmail's method of updating or can you update from you OS's repositories?

If there are some manually operations during/after package update, we will post the message on twitter (http://twitter.com/iredmail) and this forum before we push the update packages to our yum repository (for RHEL/CentOS 5.x: http://www.iredmail.org/yum/rpms/5/). If no manually operations is required, you can use yum or apt-get to update it directly & smoothly -- we use official package repositories which provided by the distribution itself.

Here is upgrade tutorial: http://code.google.com/p/iredmail/wiki/Upgrade_040_050
Warning: It is still being worked on, please do NOT apply it now.

And there won't be a upgrade tutorial for upgrading from 0.5-beta/rc.

0.5.0-stable will be released Aug 15.

I've just come across your awesome scripts and am thinking very seriously about migrating my small mail server over to iredmail after trialling it on a vps that I have access to.

However I have a couple of questions that I'd like to understand a bit more fully.

What happens when a component gets a new version? (e.g. Dovecot already has a new version v1.1.18 that isn't part of 0.5.0rc2 ) Are you tied to the iredmail's method of updating or can you update from you OS's repositories?

Will updating from v0.4 to v0.5 be documented fully? How about updating from the 0.5 betas?

Finally, what sort of a release cycle are you aiming for?

Thanks in advance,
TalusMaximus