Hi Owen,<br><br><div class="gmail_quote">On Tue, Oct 27, 2009 at 10:34 AM, Owen Leonard <span dir="ltr"><<a href="mailto:oleonard@myacpl.org">oleonard@myacpl.org</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">> Note that writing to one of the lists, petitioning for "some LibLimer" to<br>
> respond is not as effective at getting our attention as is writing us<br>
> directly as you have done in the past.<br>
<br>
</div>Better yet, you could grant Release Managers and Release Maintainers<br>
direct access to edit the relevant areas of Koha.org and permission to<br>
load release files on <a href="http://download.koha.org" target="_blank">download.koha.org</a>.<br></blockquote><div><a href="http://download.koha.org">download.koha.org</a> is a site that LibLime created to provide a historical archive of Koha releases done to date. It currently resides on LibLime servers that have other web sites so we're not able to provide direct shell/ftp access at this time.</div>
<div><br></div><div>That said, we are committed to triggering any upload request within 6 hours or receipt.</div><div><br></div><div>While an interesting idea, providing direct access to <a href="http://download.koha.org">download.koha.org</a> as you suggest would not have solved the problems that occurred with this last release of 3.00.04. I documented the correct procedure for rolling a Koha release in the misc/release_notes/README.txt file and following that procedure is the best way to ensure that future releases do not suffer the same confusion.</div>
<div><br></div><div>Sincerely,</div><div><br></div><div>Josh</div><div><br></div></div>-- <br>Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE<br>CEO migration, training, maintenance, support<br>
LibLime Featuring Koha Open-Source ILS<br><a href="mailto:jmf@liblime.com">jmf@liblime.com</a> |Full Demos at <a href="http://liblime.com/koha">http://liblime.com/koha</a> |1(888)KohaILS<br>