From pate@eylerfamily.org Wed Jun 18 17:22:52 2003 From: Pat Eyler To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Re: [Koha] 3rd pre 2.0 meeting (fwd) Date: Wed, 18 Jun 2003 17:23:21 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8958327490542974837==" --===============8958327490542974837== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable hmm, this was really meant for the list at large, not just Ed. sorry, -pate ---------- Forwarded message ---------- Date: Wed, 18 Jun 2003 20:21:56 -0400 (EDT) From: Pat Eyler To: COURYHOUSE@aol.com Subject: Re: [Koha-devel] Re: [Koha] 3rd pre 2.0 meeting On Wed, 18 Jun 2003 COURYHOUSE@aol.com wrote: > Unfortunately my compatriots do not=EF=BF=BD invest time in futures. We nee= d to make > sure they do not wander off to another system\ having them onboard will add > even more Fame to KOHA. I'm sorry that they're not willing to work toward the solution that they want. Making a bit of an elbow grease investment in 2.0.0 would likely pay back in terms of a better 2.0.1 (with the things they want in it) sooner rather than later. > > they are looking=EF=BF=BD for something that is complete,=EF=BF=BD in the f= ollowing areas.. > > marc import > > marc export > > LC call numbers. > > I assume the other items are all done, but the third one is a necessity too. Yes, the first to are done (subject at this point only to finding and eliminating bugs). > > No one even wants to play with Dewey screens=EF=BF=BD and start loading the= catalog > when what they need is LC. > > It is my belief that the LC item needs to be expedited=EF=BF=BD so those in= the > university and scientific community can start to work. > Ed, we're probably less than 2 months from 2.0.0, the more people who can find and report bugs (and fix them) the faster we can get 2.0.0 out the door. Once 2.0.0 has been put to bed, we can start on 2.0.1. I'm guessing that 2.0.1 will be a much shorter cycle than 2.0.0 (on the order 3 months or less -- no promises though). If you absolutely, positively can't wait until then, you have a couple of choices. The code is freely available and the changes you're looking for aren't too big, you could write them yourself or hire someone to write them. I'm sure that Paul will be happy to accept a big block of changes for 2.0.1 once development starts. I hate to sound negative about this, but it's an important point. Koha exists because people who have wanted specific things have stepped up and done them (sometimes by hiring developers). We're working very hard to get a rock-solid 2.0.0 done in a timely fashion so that we can get back to work on new development. That's the sandbox we all want to be playing in. thanks, -pate > thanks Ed Sharpe archivist for SMECC > ed sharpe archivist for smecc > > Subj: Re: [Koha-devel] Re: [Koha] 3rd pre 2.0 meeting=EF=BF=BD > > Date: 6/18/2003 3:28:54 PM US Mountain Standard Time > > From: chicks@chicks.net > > To: COURYHOUSE@aol.com > > CC: koha@lists.katipo.co.nz, koha-devel@lists.sourc= eforge.net > > Sent from the Internet > > > > > > > > On Wed, 18 Jun 2003 COURYHOUSE@aol.com wrote: > > >OK so it is still not going to be useable=EF=BF=BD by our community for = a while > > then. > > >Ultra bummer. now I have 30 sad news emails to send out. > > > > It doesn't have to be sad news emails!=EF=BF=BD It's just a matter of tim= ing.=EF=BF=BD > > You can play with 2.0 koha while waiting for 2.0.1 to get familiar with > > Koha and discover any other issues you may need fixed.=EF=BF=BD By the ti= me 2.0.1 > > comes out you'll be ready to consider a beta schedule and projected > > production date.=EF=BF=BD Plus actively testing 2.0 until the next minor = release > > comes will almost certainly help 2.0.1 arrive sooner.=EF=BF=BD What sadne= ss? > > > --===============8958327490542974837==--