Personally, I'm a 2. I can't say what John or Cindy would prefer. But it looks like we'll be rolling out with dev_week in a matter of weeks, so I'd rather wait until 3.0 is more polished code-wise since we are no longer waiting for
3.0 before making our transition.<br><br>Kyle<br><br><div><span class="gmail_quote">On 3/21/07, <b class="gmail_sendername">MJ Ray</b> <<a href="mailto:mjr@phonecoop.coop">mjr@phonecoop.coop</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This is a translation of the email of Wed, 21 Mar 2007 11:25:44 +0100<br>from paul POULAIN to koha-Infos. The original is at<br><a href="http://ob.paulpoulain.com/pipermail/infos/Week-of-Mon-20070319/002112.html">http://ob.paulpoulain.com/pipermail/infos/Week-of-Mon-20070319/002112.html
</a><br>if you want to spot my mistranslations.<br><br>*I would like to hear global-list views on the 1 / 2 / 3 survey below.*<br><br><br>So, the message from paul POULAIN:<br><br>Hello,<br><br>As usual, I'm going to give you some news of Koha
3.0. *The second<br>part of this email is extremely important for the users among you.*<br><br>Progress<br>========<br><br>* Joshua (the release manage for v3.0) and his company LibLibe have<br>started tests on this version. He's found some bugs, as expected, but
<br>finds that it's in an encouraging shape.<br><br>The installer has been developed by Henri-Damien as his construction<br>job: once the sysadmin installation is done, the initial configuration<br>(language, MARC type, catalogue tables, ...) are set through a web
<br>interface. It's very practical and more than that, it can be extended<br>easily. We can therefore give "public library" example settings, a<br>"society trust" example, that can be installed in a few clicks.
<br><br>The hosting platform for koha development (<a href="http://savannah.gnu.org">savannah.gnu.org</a>) had a<br>very large problem at the start of the month. In summary, multiple<br>disks broke simultaneously. It required three days to bring the
<br>platform back up. But more annoying, it's lost two days of work in<br>the meantime. Everyone has had to commit their work of those two days<br>anew (this concerned LibLime more than anyone in fact, but was within
<br>36hours of causing me problems...) In short, a good week of loss, lots<br>of energy and stress.<br><br>Continuing work (and the survey)<br>===============<br><br>Joshua (and it's his role as release manager) would like to improve
<br>three things before releasing the version:<br><br>1- fix the bugs. No-one can dispute the necessity of that.<br><br>2- Finish the code cleanup. Antoine, who worked for me for four<br>months on this, didn't finish 100% of the work. That won't change
<br>anything much for the user, but, in the long term, it's important: it<br>makes for a more stable software, easier to develop and perhaps also<br>more attractive for other contributors. And then 90% of the work is
<br>already done, with 10% to do.<br><br>3- Revise all the templates to make something very polished. He<br>proposes to use YUI (Yahoo User Interface), some components "freed" by<br>Yahoo that we can therefore integrate. Graphically, that will give
<br>something like <a href="http://kados.org/stuff/yui_borrowers.png">http://kados.org/stuff/yui_borrowers.png</a> and<br><a href="http://kados.org/stuff/moremember.png">http://kados.org/stuff/moremember.png</a> - pretty, isn't it?
<br><br>There is a problem in doing all that: the time that it takes. Joshua<br>doesn't know enough to estimate that for the moment and me neither.<br>But I'm certain that it won't take days or weeks, but months.
<br><br>Now, some among you are waiting for Koha 3.0 with barely-contained<br>impatience. As I've always promised to put the users first, I ask<br>your opinion:<br><br>1- Argh! We must release Koha 3.0 as soon as possible. The code
<br>clean-up concerns you developers alone, so do it afterwards. And the<br>improvement of user interface can wait too. But I need 3.0's features<br>now!<br><br>2- Damn! Bad news. But good, we're working with
2.2 well enough and<br>we can wait 3 months more. But not more than 3 months, even so.<br><br>3- Pah! I'm very happy with Koha 2.2. Koha 3.0 can take another 6<br>months to arrive and I won't be unhappy.<br><br>
You can just reply 1 / 2 / 3, but you can also say more. It's<br>essential that you reply, as many as possible, so I will know in which<br>direction the francophone community points and so communicate it to<br>Joshua (who reads us otherwise, even we must translate because he
<br>doesn't speak French ;-) ).<br><br>I say that the argument "there's bug XXX in Koha 2.2, so I want koha<br>3.0" isn't good - if there's a bug in 2.2, we'll fix it in 2.2.x!<br><br>PS: to reassure Pascale Nalon, who's done the translation to VF: this
<br>shouldn't impact the translation, or very marginally.<br><br>Translatedly,<br>--<br>MJ Ray - see/vidu <a href="http://mjr.towers.org.uk/email.html">http://mjr.towers.org.uk/email.html</a><br>Webmaster/web developer, statistician, sysadmin, online shop maker,
<br>developer of koha, debian, gobo, gnustep, various mail and web s/w.<br>Workers co-op @ Weston-super-Mare, Somerset <a href="http://www.ttllp.co.uk/">http://www.ttllp.co.uk/</a><br>_______________________________________________
<br>Koha mailing list<br><a href="mailto:Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a><br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br></blockquote>
</div><br><br clear="all"><br>-- <br>IT Tech<br>Crawford County Federated Library System