- Koha-devel - lists.koha-community.org

RE: FW: [Koha-devel] buildrelease for 1.3.0 => steve ?
by Eyler, Patrick 20 Sep '02

20 Sep '02

> -----Original Message----- > From: Tonnesen Steve [mailto:tonnesen@cmsd.bc.ca] > Sent: Friday, September 20, 2002 8:41 AM > To: Eyler, Patrick > Cc: koha-devel(a)lists.sourceforge.net > Subject: RE: FW: [Koha-devel] buildrelease for 1.3.0 => steve ? > > > On Fri, 20 Sep 2002, Eyler, Patrick wrote: > > > Let's build a 1.4-unstable package to put it in. I think the 1.2 > series > > will likely continue to get some love until (at least) next summer > > (people will take a while to upgrade), and I'd like us to be able > to > > support both trees in the interim. v> > 1.4-unstable should maybe be used for 1.4 release candidates? We > should > have a koha_1.3 package for the 1.3.x releases. > I wanted to reinforce the idea that the whole 1.3 series is the unstable/development cycle for 1.4 .... my thought is that it will go something like this: 1.3.0, ... 1.3.X, 1.4.0RC1, 1.4.0RC2, 1.4.0, 1.4.1RC1, ... 1.4.0, 1.4.1, etc would be in the koha_1.4 package and everything else would go into koha_1.4_unstable I'm open to discussion, and I think the final call belongs to Paul (he's the release manager after all). -pate > Steve. >

1 0

RE: FW: [Koha-devel] buildrelease for 1.3.0 => steve ?
by Eyler, Patrick 20 Sep '02

20 Sep '02

Steve wrote: > On Fri, 20 Sep 2002, Eyler, Patrick wrote: > > Paul asked: > > > Then, should I tag the version ? I think yes. Please confirm. > Yes, tag the release if you are going to release it publicly. This will > allow us to see what has changed in CVS since it was released for bug > confirmation, etc. We can also delete old tags after a certain time so > they don't clutter up the CVS too much. For example, I deleted all of the > release candidates for the 1.2.2 release after 1.2.2 went out. > > > where should I put my tar.gz when builded ? we planned not to release > > > officialy it on sf, so where should I put it after testing install ? > > > > Do we want to put it on sourceforge? I think that might be a good idea. > > We can also make release announcements on Freshmeat. I think that > > active, visible development of the 1.4 tree will draw even more > > developers into the fold. > I'd recommend putting it up on sourceforge. Put it under the > koha-unstable package, I guess. Or do we want a new package for 1.3.x > releases to separate them from the release candidates for the stable > branch? Only the most recent file in a package will show up on the main > sf.net/projects/koha/ page. Let's build a 1.4-unstable package to put it in. I think the 1.2 series will likely continue to get some love until (at least) next summer (people will take a while to upgrade), and I'd like us to be able to support both trees in the interim. > Steve. -pate

2 1

FW: [Koha-devel] buildrelease for 1.3.0 => steve ?
by Eyler, Patrick 20 Sep '02

20 Sep '02

Oops, this should have gone to the list as well... bad outlook, no cookie for you! -pate -----Original Message----- From: Eyler, Patrick Sent: Friday, September 20, 2002 7:59 AM To: 'paul POULAIN' Subject: RE: [Koha-devel] buildrelease for 1.3.0 => steve ? -----Original Message----- From: paul POULAIN [mailto:paul.poulain@free.fr] Sent: Friday, September 20, 2002 7:39 AM To: koha-devel(a)lists.sourceforge.net Subject: [Koha-devel] buildrelease for 1.3.0 => steve ? > Hi, > I try to build a 1.3.0 tarball (wooow !) with the buildrelease script. Wow! This is awesome! > I don't understand well how it manages versions. > I'im in my koha.dev (main trunk) directory. > the script says : > Current release tag is 1.2.3RC14. > Would you like to bump that up to 1.2.3RC15 (or manually enter > version)? [Y]/N: > Should I answer N or Y ? > I found that N build a new 1.2.3RC15 and a Y enables a new version. In > this case, what shall I enter ? 1.3.0RC1 or 1.3.0 ? I think that we can just use 1.3.0, with the development releases, everyone knows that they are potentially broken anyway. Once we go into a 1.4.0 release cycle we can go back to doing RC releases. > Then, should I tag the version ? I think yes. Please confirm. > where should I put my tar.gz when builded ? we planned not to release > officialy it on sf, so where should I put it after testing install ? Do we want to put it on sourceforge? I think that might be a good idea. We can also make release announcements on Freshmeat. I think that active, visible development of the 1.4 tree will draw even more developers into the fold. > thanks for your answers and good week end to everybody thanks for all the work. Enjoy your weekend. Happy hacking, -pate > -- > Paul ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel

2 1

buildrelease for 1.3.0 => steve ?
by paul POULAIN 20 Sep '02

20 Sep '02

Hi, I try to build a 1.3.0 tarball (wooow !) with the buildrelease script. I don't understand well how it manages versions. I'im in my koha.dev (main trunk) directory. the script says : Current release tag is 1.2.3RC14. Would you like to bump that up to 1.2.3RC15 (or manually enter version)? [Y]/N: Should I answer N or Y ? I found that N build a new 1.2.3RC15 and a Y enables a new version. In this case, what shall I enter ? 1.3.0RC1 or 1.3.0 ? Then, should I tag the version ? I think yes. Please confirm. where should I put my tar.gz when builded ? we planned not to release officialy it on sf, so where should I put it after testing install ? thanks for your answers and good week end to everybody -- Paul

1 0

support for Koha in France
by nicolas morin 20 Sep '02

20 Sep '02

Hello, I am working along with Paul Poulain to get support for Koha in France. I recently tried to lobby the French national school for librarianship into supporting Koha. One of their department sounds interested : the Research department conducts researches in librarianship and information sciences. But the thing is : they might be willing to put money into the development of features that clearly are not what most common ILS provide, but not to put money on, say, MARC development. That makes sense for them, since they are a research department. But what Koha needs most, I think, is money to help develop the "usual" features : MARC, Z3950, etc... So : could we come up with something we might be interested in, that would also interest them, a feature at the cutting edge of library systems that would also make sense for Koha to develop? For instance, I thought they might be interested in a system that is truly multilingual, were you can store data in arabic, english, french, chinese, whatever; an Opac you can search in all these languages... It's the only example I could come up with. Any other idea? Any input welcome... Nicolas

1 0

Re: [Koha] Database Structure and Full Features
by Pat Eyler 19 Sep '02

19 Sep '02

Domingo, This question may get more responses from the developers' list. (I'm CC:ing it there.) If you have further technical questions, please feel free to subscribe to the list (see http://www.sourceforge.net/projects/koha for directions) and post them there. I'm sure that you'll find the answers that your looking for. (Maybe whoever answers them would like to do so publicly, and we'll turn your answer into docs on the website <hint>). thanks, -pate Pat Eyler Kaitiaki/manager migrant Linux sys admin the Koha project ruby, shell, and perl geek http://www.koha.org http://pate.eylerfamily.org On Thu, 19 Sep 2002, Domingo Genaro P. Tamayo wrote: > Good day folks! > > We're currently evaluating KOHA as a solution for the Union Catalog > project of the SciNET (Science Network) here in the Philippines. I'm > interested with the database structure and the detailed features of KOHA. > I tried searching koha's site but I can't find those information. > I believe KOHA is an excellent system. I just hope anyone can help me find > the data that I need. > Regards, > > Domingo Genaro P. Tamayo > STII-DOST > > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha >

1 0

KohaCD
by Tonnesen Steve 19 Sep '02

19 Sep '02

I've managed to get X and Opera working on a 114MB CD image. I hope to upload a copy of this tomorrow. Auto configuration of X works with my intel i815 video card, but that's all I've tested it with. I tested on two different models of computer and they _both_ had i815 cards in them. I'll try to test a couple of other makes tomorrow, and see if I can't find some other cards. Steve.

1 0

[Bug 102] New: Current issues list is not showing the "itemtype"
by bugzilla-daemon＠wilbur.katipo.co.nz 19 Sep '02

19 Sep '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=102 Summary: Current issues list is not showing the "itemtype" Product: Koha Version: 1.2.3 Platform: PC Status: NEW Severity: normal Priority: P2 Component: Members AssignedTo: chris(a)katipo.co.nz ReportedBy: tonnesen(a)cmsd.bc.ca QAContact: koha-devel(a)lists.sourceforge.net This is on the members page. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 96] Various installer.pl fixes
by bugzilla-daemon＠wilbur.katipo.co.nz 19 Sep '02

19 Sep '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=96 tonnesen(a)cmsd.bc.ca changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-09-20 07:35 ------- Fixes applied to installer.pl and Install.pm in the rel-1-2 branch of CVS. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 101] circulation error
by bugzilla-daemon＠wilbur.katipo.co.nz 18 Sep '02

18 Sep '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=101 tonnesen(a)cmsd.bc.ca changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-09-19 10:54 ------- Fixed in CVS. added an undef where the database handle would have been and checked that dbh was defined in calc_charges, otherwise it opens a new handle. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0