<div class="gmail_quote">On 8 June 2010 14:06, Robyn Bergeron <span dir="ltr"><<a href="mailto:robyn.bergeron@gmail.com">robyn.bergeron@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">> The upgrade process for Zikula 1.2.3 is just a matter of<br>
> a) copy new files<br>
> b) run upgrade.php<br>
> c) delete install*, upgrade.php<br>
> This will not affect your AuthFAS at all.<br>
> To upgrade EZComments, simply copy the new module files, then go to the<br>
> admin -> modules ->regenerate list, then click upgrade on the EZComments<br><br>
</div>Perhaps someone can clear some things up for me before I stick my foot<br>
further into my mouth. :)<br></blockquote><div><br></div><div>Well, I dont know the overhead of your .rpm creation process, but upgrading a site will take 5 minutes.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
* How long will this upgrade take us (not the physical typing of<br>
things and copying files, but builds / packaging / whatever magic<br>
needs to hapen) - can we get this up and running by Wednesday, Friday,<br>
?, for basic testing to see if this will fix the EZComments issue?<br>
* When 1.2.3 goes into staging and/or production - would we really be<br>
installing an old version, then upgrading to 1.2.3, following the<br>
steps above? Or would it be advisable to install 1.2.3 from scratch?<br>
If so, would we want to just install 1.2.3 from scratch in a new<br>
instance on pt6, so that we can have a documented, repeatable<br>
process?</blockquote><div><br></div><div>For the future, I would really like to start some continuous integration process for packaging - this was maintainers can simply review the created packages and push them rather than have to spend time doing everything manually.</div>
<div> </div><div>Regards,</div><div><br></div><div>Drak</div></div>