From: Andrew N. <as...@gm...> - 2009-10-27 15:54:38
|
So - as pointed out by Till in an email on vufind-general, many folks are on RC1 which is becoming very out dated ("obsolete" was Till's word). We still have quite a few major tasks for RC2 release. As much as I hate to say it - should we create an RC3 milestone and move some of the work that needs more time to RC3 so we can get an RC2 release out? I think this might also help buy some credibility from the library community since VuFind has not seen a release in a long time. Thoughts? Andrew |
From: Demian K. <dem...@vi...> - 2009-10-27 16:36:34
|
Personally, I don't think an RC3 milestone is necessary -- I'd be more inclined to shift more items from RC2 to 1.0 if we feel we absolutely can't get everything done in time. I also don't think the remaining RC2 tasks are necessarily all that major. I've been on the verge of sending an email proposing that we set an official release date for RC2 -- I guess now is as good a time as any to start that discussion. I personally think we should have something releasable by the end of the year, so a mid-December date might be reasonable. Honestly, I think the current trunk has already reached the point where it's superior to RC1 even with a few known problems. To back up my "by the end of the year" proposal, the bottom of this email contains my thoughts on the remaining JIRA issues, grouped into clusters. Am I missing anything? Does anyone feel more pessimistic than I do? One other thought -- if there's anybody on the list who hasn't been working with the latest trunk code, now would be a good time to start if you have the time. It would be helpful to have some fresh eyes on this to catch any new issues that the rest of us have missed. thanks, Demian WORK DEFINITELY NEEDED: Tag search consistency (VUFIND-106): Greg has already improved this with the Search Object. There's still some weirdness that needs to be cleaned up, but I plan on taking care of it soon -- shouldn't be more than a couple of hours to get to basic acceptable behavior. Advanced, complex tag searching is a bigger issue that I think is beyond the scope of RC2 -- we'll deal with that later. Other Search Object Issues (VUFIND-5, VUFIND-134, VUFIND-145, VUFIND-142): Greg's making pretty steady progress on Search Object changes, and I'm happy to pick up slack if needed. I don't think any of the remaining issues are very big -- the hard part is behind us. XSS Issues (VUFIND-54): This issue is never going to totally go away -- there will always be chinks in our armor that need patching. We've already fixed many of the most obvious of these problems, and I'll do a full review of templates in the next couple of weeks to catch remaining problems. No matter how far we get, RC2 will be better than RC1 in this regard. RC1 -> RC2 Upgrade Script (VUFIND-132): Till and Greg have already done good work on this. I plan on testing it and possibly adding some more paranoid error handling when we get closer to RC2 release time. Caching Issues (VUFIND-146): This is a very new issue and already has some comments on it in JIRA -- I expect this will be resolved fairly quickly. EASY TO DEFER FOR 1.0 IF NECESSARY: Finalize Admin Module (VUFIND-10): This is a bonus feature. If we can get it done, great. If not, we can turn off the bits that don't work yet. SolrMarc Issues (VUFIND-115): The new SolrMarc binary resolves a handful of problems noted in JIRA (many not actually scheduled for RC2 release). I'm making good progress on implementing this in my branch, so we may be able to merge it into an RC2 release. If that doesn't happen in time, I don't think this is a show-stopper. Advanced Search Limits (VUFIND-139): The most blatant problems here are already fixed. The illustration indexing needs some work, and I plan on trying to improve it using the scripting capabilities of the new SolrMarc release. If we get the new SolrMarc into RC2, this last detail can be fixed in RC2. If we opt not to do that, we're still better off than we were in RC1, and we can make deeper improvements later. IE CSS Problems in Browse Mode (VUFIND-91): This is a cosmetic issue that I would like to see fixed... but if we don't get that far, it doesn't impede functionality and it could certainly be worse. Haven't heard if Chris Barr is able to devote any time to this, but if he isn't, I can look at it. I already decided to just bite the bullet and fix the more serious VUFIND-90 CSS problem myself. POSSIBLY ALREADY RESOLVED: Implement 1.0 Default Theme (VUFIND-11): I believe this is done, but I haven't closed it since I'm not sure if Andrew's aware of some details I'm missing. Any objections to considering this finished at this point? File_MARC Exception Problem (VUFIND-6): I'm not sure how to reproduce this or whether it still even applies to our code. Andrew, do you know anything about the status? From: Andrew Nagy [mailto:as...@gm...] Sent: Tuesday, October 27, 2009 11:54 AM To: vuf...@li... Subject: [Vufind-admins] RC2 Release So - as pointed out by Till in an email on vufind-general, many folks are on RC1 which is becoming very out dated ("obsolete" was Till's word). We still have quite a few major tasks for RC2 release. As much as I hate to say it - should we create an RC3 milestone and move some of the work that needs more time to RC3 so we can get an RC2 release out? I think this might also help buy some credibility from the library community since VuFind has not seen a release in a long time. Thoughts? Andrew |
From: Tim M. <tmm8@Lehigh.EDU> - 2009-10-27 17:02:25
|
Where does support for Dewey call numbering fit into the list below? Tim Tim McGeary Team Leader, Library Technology Lehigh University 610-758-4998 tim...@le... GTalk/Yahoo/Skype: timmcgeary Demian Katz wrote: > Personally, I don't think an RC3 milestone is necessary -- I'd be more > inclined to shift more items from RC2 to 1.0 if we feel we absolutely > can't get everything done in time. I also don't think the remaining RC2 > tasks are necessarily all that major. > > > > I've been on the verge of sending an email proposing that we set an > official release date for RC2 -- I guess now is as good a time as any to > start that discussion. I personally think we should have something > releasable by the end of the year, so a mid-December date might be > reasonable. Honestly, I think the current trunk has already reached the > point where it's superior to RC1 even with a few known problems. > > > > To back up my "by the end of the year" proposal, the bottom of this > email contains my thoughts on the remaining JIRA issues, grouped into > clusters. Am I missing anything? Does anyone feel more pessimistic > than I do? > > > > One other thought -- if there's anybody on the list who hasn't been > working with the latest trunk code, now would be a good time to start if > you have the time. It would be helpful to have some fresh eyes on this > to catch any new issues that the rest of us have missed. > > > > thanks, > > Demian > > > > WORK DEFINITELY NEEDED: > > > > Tag search consistency (VUFIND-106): Greg has already improved this with > the Search Object. There's still some weirdness that needs to be > cleaned up, but I plan on taking care of it soon -- shouldn't be more > than a couple of hours to get to basic acceptable behavior. Advanced, > complex tag searching is a bigger issue that I think is beyond the scope > of RC2 -- we'll deal with that later. > > > > Other Search Object Issues (VUFIND-5, VUFIND-134, VUFIND-145, > VUFIND-142): Greg's making pretty steady progress on Search Object > changes, and I'm happy to pick up slack if needed. I don't think any of > the remaining issues are very big -- the hard part is behind us. > > > > XSS Issues (VUFIND-54): This issue is never going to totally go away -- > there will always be chinks in our armor that need patching. We've > already fixed many of the most obvious of these problems, and I'll do a > full review of templates in the next couple of weeks to catch remaining > problems. No matter how far we get, RC2 will be better than RC1 in this > regard. > > > > RC1 -> RC2 Upgrade Script (VUFIND-132): Till and Greg have already done > good work on this. I plan on testing it and possibly adding some more > paranoid error handling when we get closer to RC2 release time. > > > > Caching Issues (VUFIND-146): This is a very new issue and already has > some comments on it in JIRA -- I expect this will be resolved fairly > quickly. > > > > EASY TO DEFER FOR 1.0 IF NECESSARY: > > > > Finalize Admin Module (VUFIND-10): This is a bonus feature. If we can > get it done, great. If not, we can turn off the bits that don't work yet. > > > > SolrMarc Issues (VUFIND-115): The new SolrMarc binary resolves a handful > of problems noted in JIRA (many not actually scheduled for RC2 > release). I'm making good progress on implementing this in my branch, > so we may be able to merge it into an RC2 release. If that doesn't > happen in time, I don't think this is a show-stopper. > > > > Advanced Search Limits (VUFIND-139): The most blatant problems here are > already fixed. The illustration indexing needs some work, and I plan on > trying to improve it using the scripting capabilities of the new > SolrMarc release. If we get the new SolrMarc into RC2, this last detail > can be fixed in RC2. If we opt not to do that, we're still better off > than we were in RC1, and we can make deeper improvements later. > > > > IE CSS Problems in Browse Mode (VUFIND-91): This is a cosmetic issue > that I would like to see fixed… but if we don't get that far, it > doesn't impede functionality and it could certainly be worse. Haven't > heard if Chris Barr is able to devote any time to this, but if he isn't, > I can look at it. I already decided to just bite the bullet and fix the > more serious VUFIND-90 CSS problem myself. > > > > POSSIBLY ALREADY RESOLVED: > > > > Implement 1.0 Default Theme (VUFIND-11): I believe this is done, but I > haven't closed it since I'm not sure if Andrew's aware of some details > I'm missing. Any objections to considering this finished at this point? > > > > File_MARC Exception Problem (VUFIND-6): I'm not sure how to reproduce > this or whether it still even applies to our code. Andrew, do you know > anything about the status? > > > > *From:* Andrew Nagy [mailto:as...@gm...] > *Sent:* Tuesday, October 27, 2009 11:54 AM > *To:* vuf...@li... > *Subject:* [Vufind-admins] RC2 Release > > > > So - as pointed out by Till in an email on vufind-general, many folks > are on RC1 which is becoming very out dated ("obsolete" was Till's > word). We still have quite a few major tasks for RC2 release. As much > as I hate to say it - should we create an RC3 milestone and move some of > the work that needs more time to RC3 so we can get an RC2 release out? > I think this might also help buy some credibility from the library > community since VuFind has not seen a release in a long time. > > Thoughts? > > Andrew > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > > > ------------------------------------------------------------------------ > > _______________________________________________ > Vufind-admins mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-admins |
From: Demian K. <dem...@vi...> - 2009-10-27 17:11:04
|
Right now, Dewey is on the 1.0 list rather than the RC2 list. Realistically speaking, its implementation largely hinges on the SolrMarc upgrade I mention near VUFIND-115 below. Once we upgrade to the new SolrMarc, plugging in the necessary Dewey functionality will be much easier thanks to its support for writing custom external indexing scripts without recompiling the whole SolrMarc application. I'm currently working on the upgrade in the demian_solrmarc branch under SVN -- it's just about working, but I'm waiting for feedback from Bob Haschart about a couple of minor problems. Once those are addressed, I'll post more information to the vufind-tech list so we can move forward on testing and eventual reintegration with the trunk. Once the trunk is upgraded, the Dewey work I shared with you a few weeks ago can be easily incorporated into VuFind. - Demian > -----Original Message----- > From: Tim McGeary [mailto:tmm8@Lehigh.EDU] > Sent: Tuesday, October 27, 2009 1:02 PM > To: Demian Katz > Cc: Andrew Nagy; vuf...@li... > Subject: Re: [Vufind-admins] RC2 Release > > Where does support for Dewey call numbering fit into the list below? > > Tim > > Tim McGeary > Team Leader, Library Technology > Lehigh University > 610-758-4998 > tim...@le... > GTalk/Yahoo/Skype: timmcgeary > > > Demian Katz wrote: > > Personally, I don't think an RC3 milestone is necessary -- I'd be > more > > inclined to shift more items from RC2 to 1.0 if we feel we absolutely > > can't get everything done in time. I also don't think the remaining > RC2 > > tasks are necessarily all that major. > > > > > > > > I've been on the verge of sending an email proposing that we set an > > official release date for RC2 -- I guess now is as good a time as any > to > > start that discussion. I personally think we should have something > > releasable by the end of the year, so a mid-December date might be > > reasonable. Honestly, I think the current trunk has already reached > the > > point where it's superior to RC1 even with a few known problems. > > > > > > > > To back up my "by the end of the year" proposal, the bottom of this > > email contains my thoughts on the remaining JIRA issues, grouped into > > clusters. Am I missing anything? Does anyone feel more pessimistic > > than I do? > > > > > > > > One other thought -- if there's anybody on the list who hasn't been > > working with the latest trunk code, now would be a good time to start > if > > you have the time. It would be helpful to have some fresh eyes on > this > > to catch any new issues that the rest of us have missed. > > > > > > > > thanks, > > > > Demian > > > > > > > > WORK DEFINITELY NEEDED: > > > > > > > > Tag search consistency (VUFIND-106): Greg has already improved this > with > > the Search Object. There's still some weirdness that needs to be > > cleaned up, but I plan on taking care of it soon -- shouldn't be more > > than a couple of hours to get to basic acceptable behavior. > Advanced, > > complex tag searching is a bigger issue that I think is beyond the > scope > > of RC2 -- we'll deal with that later. > > > > > > > > Other Search Object Issues (VUFIND-5, VUFIND-134, VUFIND-145, > > VUFIND-142): Greg's making pretty steady progress on Search Object > > changes, and I'm happy to pick up slack if needed. I don't think any > of > > the remaining issues are very big -- the hard part is behind us. > > > > > > > > XSS Issues (VUFIND-54): This issue is never going to totally go away > -- > > there will always be chinks in our armor that need patching. We've > > already fixed many of the most obvious of these problems, and I'll do > a > > full review of templates in the next couple of weeks to catch > remaining > > problems. No matter how far we get, RC2 will be better than RC1 in > this > > regard. > > > > > > > > RC1 -> RC2 Upgrade Script (VUFIND-132): Till and Greg have already > done > > good work on this. I plan on testing it and possibly adding some > more > > paranoid error handling when we get closer to RC2 release time. > > > > > > > > Caching Issues (VUFIND-146): This is a very new issue and already has > > some comments on it in JIRA -- I expect this will be resolved fairly > > quickly. > > > > > > > > EASY TO DEFER FOR 1.0 IF NECESSARY: > > > > > > > > Finalize Admin Module (VUFIND-10): This is a bonus feature. If we > can > > get it done, great. If not, we can turn off the bits that don't work > yet. > > > > > > > > SolrMarc Issues (VUFIND-115): The new SolrMarc binary resolves a > handful > > of problems noted in JIRA (many not actually scheduled for RC2 > > release). I'm making good progress on implementing this in my > branch, > > so we may be able to merge it into an RC2 release. If that doesn't > > happen in time, I don't think this is a show-stopper. > > > > > > > > Advanced Search Limits (VUFIND-139): The most blatant problems here > are > > already fixed. The illustration indexing needs some work, and I plan > on > > trying to improve it using the scripting capabilities of the new > > SolrMarc release. If we get the new SolrMarc into RC2, this last > detail > > can be fixed in RC2. If we opt not to do that, we're still better > off > > than we were in RC1, and we can make deeper improvements later. > > > > > > > > IE CSS Problems in Browse Mode (VUFIND-91): This is a cosmetic issue > > that I would like to see fixed... but if we don't get that far, it > > doesn't impede functionality and it could certainly be worse. > Haven't > > heard if Chris Barr is able to devote any time to this, but if he > isn't, > > I can look at it. I already decided to just bite the bullet and fix > the > > more serious VUFIND-90 CSS problem myself. > > > > > > > > POSSIBLY ALREADY RESOLVED: > > > > > > > > Implement 1.0 Default Theme (VUFIND-11): I believe this is done, but > I > > haven't closed it since I'm not sure if Andrew's aware of some > details > > I'm missing. Any objections to considering this finished at this > point? > > > > > > > > File_MARC Exception Problem (VUFIND-6): I'm not sure how to reproduce > > this or whether it still even applies to our code. Andrew, do you > know > > anything about the status? > > > > > > > > *From:* Andrew Nagy [mailto:as...@gm...] > > *Sent:* Tuesday, October 27, 2009 11:54 AM > > *To:* vuf...@li... > > *Subject:* [Vufind-admins] RC2 Release > > > > > > > > So - as pointed out by Till in an email on vufind-general, many folks > > are on RC1 which is becoming very out dated ("obsolete" was Till's > > word). We still have quite a few major tasks for RC2 release. As > much > > as I hate to say it - should we create an RC3 milestone and move some > of > > the work that needs more time to RC3 so we can get an RC2 release > out? > > I think this might also help buy some credibility from the library > > community since VuFind has not seen a release in a long time. > > > > Thoughts? > > > > Andrew > > > > > > --------------------------------------------------------------------- > --- > > > > --------------------------------------------------------------------- > --------- > > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > > is the only developer event you need to attend this year. Jumpstart > your > > developing skills, take BlackBerry mobile applications to market and > stay > > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > > http://p.sf.net/sfu/devconference > > > > > > --------------------------------------------------------------------- > --- > > > > _______________________________________________ > > Vufind-admins mailing list > > Vuf...@li... > > https://lists.sourceforge.net/lists/listinfo/vufind-admins |
From: Tim M. <tmm8@Lehigh.EDU> - 2009-10-27 18:20:37
|
Two follow-up questions: 1.) Is it wise to make a SolrMarc upgrade between RC2 and 1.0? 2.) I'm a little nervous about waiting for 1.0 to release support for a call number classification that is still the most used classification in the world. Forgive me if I've missed this (I'm behind in all of the mailing lists), but what is your goal for the date of the 1.0 release? At this point, that is the major piece that we need to put VuFind in production. Everything else is gravy. Once that is in place, I can put resources into VuFind. Tim Tim McGeary Team Leader, Library Technology Lehigh University 610-758-4998 tim...@le... GTalk/Yahoo/Skype: timmcgeary Demian Katz wrote: > Right now, Dewey is on the 1.0 list rather than the RC2 list. > Realistically speaking, its implementation largely hinges on the > SolrMarc upgrade I mention near VUFIND-115 below. Once we upgrade to > the new SolrMarc, plugging in the necessary Dewey functionality will > be much easier thanks to its support for writing custom external > indexing scripts without recompiling the whole SolrMarc application. > I'm currently working on the upgrade in the demian_solrmarc branch > under SVN -- it's just about working, but I'm waiting for feedback > from Bob Haschart about a couple of minor problems. Once those are > addressed, I'll post more information to the vufind-tech list so we > can move forward on testing and eventual reintegration with the > trunk. Once the trunk is upgraded, the Dewey work I shared with you > a few weeks ago can be easily incorporated into VuFind. > > - Demian > >> -----Original Message----- From: Tim McGeary >> [mailto:tmm8@Lehigh.EDU] Sent: Tuesday, October 27, 2009 1:02 PM >> To: Demian Katz Cc: Andrew Nagy; >> vuf...@li... Subject: Re: [Vufind-admins] >> RC2 Release >> >> Where does support for Dewey call numbering fit into the list >> below? >> >> Tim >> >> Tim McGeary Team Leader, Library Technology Lehigh University >> 610-758-4998 tim...@le... GTalk/Yahoo/Skype: timmcgeary >> >> >> Demian Katz wrote: >>> Personally, I don't think an RC3 milestone is necessary -- I'd be >>> >> more >>> inclined to shift more items from RC2 to 1.0 if we feel we >>> absolutely can't get everything done in time. I also don't think >>> the remaining >> RC2 >>> tasks are necessarily all that major. >>> >>> >>> >>> I've been on the verge of sending an email proposing that we set >>> an official release date for RC2 -- I guess now is as good a time >>> as any >> to >>> start that discussion. I personally think we should have >>> something releasable by the end of the year, so a mid-December >>> date might be reasonable. Honestly, I think the current trunk >>> has already reached >> the >>> point where it's superior to RC1 even with a few known problems. >>> >>> >>> >>> To back up my "by the end of the year" proposal, the bottom of >>> this email contains my thoughts on the remaining JIRA issues, >>> grouped into clusters. Am I missing anything? Does anyone feel >>> more pessimistic than I do? >>> >>> >>> >>> One other thought -- if there's anybody on the list who hasn't >>> been working with the latest trunk code, now would be a good time >>> to start >> if >>> you have the time. It would be helpful to have some fresh eyes >>> on >> this >>> to catch any new issues that the rest of us have missed. >>> >>> >>> >>> thanks, >>> >>> Demian >>> >>> >>> >>> WORK DEFINITELY NEEDED: >>> >>> >>> >>> Tag search consistency (VUFIND-106): Greg has already improved >>> this >> with >>> the Search Object. There's still some weirdness that needs to be >>> cleaned up, but I plan on taking care of it soon -- shouldn't be >>> more than a couple of hours to get to basic acceptable behavior. >> Advanced, >>> complex tag searching is a bigger issue that I think is beyond >>> the >> scope >>> of RC2 -- we'll deal with that later. >>> >>> >>> >>> Other Search Object Issues (VUFIND-5, VUFIND-134, VUFIND-145, >>> VUFIND-142): Greg's making pretty steady progress on Search >>> Object changes, and I'm happy to pick up slack if needed. I >>> don't think any >> of >>> the remaining issues are very big -- the hard part is behind us. >>> >>> >>> >>> XSS Issues (VUFIND-54): This issue is never going to totally go >>> away >> -- >>> there will always be chinks in our armor that need patching. >>> We've already fixed many of the most obvious of these problems, >>> and I'll do >> a >>> full review of templates in the next couple of weeks to catch >> remaining >>> problems. No matter how far we get, RC2 will be better than RC1 >>> in >> this >>> regard. >>> >>> >>> >>> RC1 -> RC2 Upgrade Script (VUFIND-132): Till and Greg have >>> already >> done >>> good work on this. I plan on testing it and possibly adding some >>> >> more >>> paranoid error handling when we get closer to RC2 release time. >>> >>> >>> >>> Caching Issues (VUFIND-146): This is a very new issue and already >>> has some comments on it in JIRA -- I expect this will be resolved >>> fairly quickly. >>> >>> >>> >>> EASY TO DEFER FOR 1.0 IF NECESSARY: >>> >>> >>> >>> Finalize Admin Module (VUFIND-10): This is a bonus feature. If >>> we >> can >>> get it done, great. If not, we can turn off the bits that don't >>> work >> yet. >>> >>> >>> SolrMarc Issues (VUFIND-115): The new SolrMarc binary resolves a >> handful >>> of problems noted in JIRA (many not actually scheduled for RC2 >>> release). I'm making good progress on implementing this in my >> branch, >>> so we may be able to merge it into an RC2 release. If that >>> doesn't happen in time, I don't think this is a show-stopper. >>> >>> >>> >>> Advanced Search Limits (VUFIND-139): The most blatant problems >>> here >> are >>> already fixed. The illustration indexing needs some work, and I >>> plan >> on >>> trying to improve it using the scripting capabilities of the new >>> SolrMarc release. If we get the new SolrMarc into RC2, this last >>> >> detail >>> can be fixed in RC2. If we opt not to do that, we're still >>> better >> off >>> than we were in RC1, and we can make deeper improvements later. >>> >>> >>> >>> IE CSS Problems in Browse Mode (VUFIND-91): This is a cosmetic >>> issue that I would like to see fixed... but if we don't get that >>> far, it doesn't impede functionality and it could certainly be >>> worse. >> Haven't >>> heard if Chris Barr is able to devote any time to this, but if he >>> >> isn't, >>> I can look at it. I already decided to just bite the bullet and >>> fix >> the >>> more serious VUFIND-90 CSS problem myself. >>> >>> >>> >>> POSSIBLY ALREADY RESOLVED: >>> >>> >>> >>> Implement 1.0 Default Theme (VUFIND-11): I believe this is done, >>> but >> I >>> haven't closed it since I'm not sure if Andrew's aware of some >> details >>> I'm missing. Any objections to considering this finished at this >>> >> point? >>> >>> >>> File_MARC Exception Problem (VUFIND-6): I'm not sure how to >>> reproduce this or whether it still even applies to our code. >>> Andrew, do you >> know >>> anything about the status? >>> >>> >>> >>> *From:* Andrew Nagy [mailto:as...@gm...] *Sent:* Tuesday, >>> October 27, 2009 11:54 AM *To:* >>> vuf...@li... *Subject:* [Vufind-admins] >>> RC2 Release >>> >>> >>> >>> So - as pointed out by Till in an email on vufind-general, many >>> folks are on RC1 which is becoming very out dated ("obsolete" was >>> Till's word). We still have quite a few major tasks for RC2 >>> release. As >> much >>> as I hate to say it - should we create an RC3 milestone and move >>> some >> of >>> the work that needs more time to RC3 so we can get an RC2 release >>> >> out? >>> I think this might also help buy some credibility from the >>> library community since VuFind has not seen a release in a long >>> time. >>> >>> Thoughts? >>> >>> Andrew >>> >>> >>> --------------------------------------------------------------------- >>> >> --- >>> --------------------------------------------------------------------- >>> >> --------- >>> Come build with us! The BlackBerry(R) Developer Conference in SF, >>> CA is the only developer event you need to attend this year. >>> Jumpstart >> your >>> developing skills, take BlackBerry mobile applications to market >>> and >> stay >>> ahead of the curve. Join us from November 9 - 12, 2009. Register >>> now! http://p.sf.net/sfu/devconference >>> >>> >>> --------------------------------------------------------------------- >>> >> --- >>> _______________________________________________ Vufind-admins >>> mailing list Vuf...@li... >>> https://lists.sourceforge.net/lists/listinfo/vufind-admins > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your developing skills, take BlackBerry mobile applications to market > and stay ahead of the curve. Join us from November 9 - 12, 2009. > Register now! http://p.sf.net/sfu/devconference > _______________________________________________ Vufind-admins mailing > list Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-admins > |
From: Andrew N. <as...@gm...> - 2009-10-29 02:10:25
|
On Tue, Oct 27, 2009 at 12:36 PM, Demian Katz <dem...@vi...>wrote: > POSSIBLY ALREADY RESOLVED: > > > Implement 1.0 Default Theme (VUFIND-11): I believe this is done, but I > haven't closed it since I'm not sure if Andrew's aware of some details I'm > missing. Any objections to considering this finished at this point? > > Im going to close this out. Any issues regarding the new Default theme should be opened as new bugs. > > > File_MARC Exception Problem (VUFIND-6): I'm not sure how to reproduce this > or whether it still even applies to our code. Andrew, do you know anything > about the status? > I think this is solved. Im going to close it and see if I can add a try/catch for the exception so the page won't fail if this does still occur. Andrew > > > *From:* Andrew Nagy [mailto:as...@gm...] > *Sent:* Tuesday, October 27, 2009 11:54 AM > *To:* vuf...@li... > *Subject:* [Vufind-admins] RC2 Release > > > > So - as pointed out by Till in an email on vufind-general, many folks are > on RC1 which is becoming very out dated ("obsolete" was Till's word). We > still have quite a few major tasks for RC2 release. As much as I hate to > say it - should we create an RC3 milestone and move some of the work that > needs more time to RC3 so we can get an RC2 release out? I think this might > also help buy some credibility from the library community since VuFind has > not seen a release in a long time. > > Thoughts? > > Andrew > |
From: Till K. <kin...@gm...> - 2009-10-27 17:02:32
|
Andrew Nagy schrieb: > So - as pointed out by Till in an email on vufind-general, many folks > are on RC1 which is becoming very out dated ("obsolete" was Till's > word). Isn't it? RC1 shares few with the current trunk. We have a new user interface, the DisMax handlers, SearchObject, new authentication methods... If starting with VuFind now, many of the things one may learn in RC1 will be different in RC2. And running RC1 forever isn't a good idea either, I think. > We still have quite a few major tasks for RC2 release. What are the major tasks? Looking at the Jira list I only get a vague feeling... For some tasks the status seems pretty unclear to me (eg VUFIND-11, I'd say that's done, though I am not sure if there are any glitches to be fixed in the default interface, if so: which?). Maybe we should put some monkeys in front of a trunk checkout to do testing, record all unexpected errors, fix those and roll it out... ? :-) After that we finally may switch to real development branches and a stable trunk... Till |
From: Tim M. <tim.mcgeary@Lehigh.EDU> - 2009-10-27 18:11:11
|
Two follow-up questions: 1.) Is it wise to make a SolrMarc upgrade between RC2 and 1.0? 2.) I'm a little nervous about waiting for 1.0 to release support for a call number classification that is still the most used classification in the world. Forgive me if I've missed this (I'm behind in all of the mailing lists), but what is your goal for the date of the 1.0 release? At this point, that is the major piece that we need to put VuFind in production. Everything else is gravy. Once that is in place, I can put resources into VuFind. Tim Tim McGeary Team Leader, Library Technology Lehigh University 610-758-4998 tim...@le... GTalk/Yahoo/Skype: timmcgeary Demian Katz wrote: > Right now, Dewey is on the 1.0 list rather than the RC2 list. > Realistically speaking, its implementation largely hinges on the > SolrMarc upgrade I mention near VUFIND-115 below. Once we upgrade to > the new SolrMarc, plugging in the necessary Dewey functionality will > be much easier thanks to its support for writing custom external > indexing scripts without recompiling the whole SolrMarc application. > I'm currently working on the upgrade in the demian_solrmarc branch > under SVN -- it's just about working, but I'm waiting for feedback > from Bob Haschart about a couple of minor problems. Once those are > addressed, I'll post more information to the vufind-tech list so we > can move forward on testing and eventual reintegration with the > trunk. Once the trunk is upgraded, the Dewey work I shared with you > a few weeks ago can be easily incorporated into VuFind. > > - Demian > >> -----Original Message----- From: Tim McGeary >> [mailto:tmm8@Lehigh.EDU] Sent: Tuesday, October 27, 2009 1:02 PM >> To: Demian Katz Cc: Andrew Nagy; >> vuf...@li... Subject: Re: [Vufind-admins] >> RC2 Release >> >> Where does support for Dewey call numbering fit into the list >> below? >> >> Tim >> >> Tim McGeary Team Leader, Library Technology Lehigh University >> 610-758-4998 tim...@le... GTalk/Yahoo/Skype: timmcgeary >> >> >> Demian Katz wrote: >>> Personally, I don't think an RC3 milestone is necessary -- I'd be >>> >> more >>> inclined to shift more items from RC2 to 1.0 if we feel we >>> absolutely can't get everything done in time. I also don't think >>> the remaining >> RC2 >>> tasks are necessarily all that major. >>> >>> >>> >>> I've been on the verge of sending an email proposing that we set >>> an official release date for RC2 -- I guess now is as good a time >>> as any >> to >>> start that discussion. I personally think we should have >>> something releasable by the end of the year, so a mid-December >>> date might be reasonable. Honestly, I think the current trunk >>> has already reached >> the >>> point where it's superior to RC1 even with a few known problems. >>> >>> >>> >>> To back up my "by the end of the year" proposal, the bottom of >>> this email contains my thoughts on the remaining JIRA issues, >>> grouped into clusters. Am I missing anything? Does anyone feel >>> more pessimistic than I do? >>> >>> >>> >>> One other thought -- if there's anybody on the list who hasn't >>> been working with the latest trunk code, now would be a good time >>> to start >> if >>> you have the time. It would be helpful to have some fresh eyes >>> on >> this >>> to catch any new issues that the rest of us have missed. >>> >>> >>> >>> thanks, >>> >>> Demian >>> >>> >>> >>> WORK DEFINITELY NEEDED: >>> >>> >>> >>> Tag search consistency (VUFIND-106): Greg has already improved >>> this >> with >>> the Search Object. There's still some weirdness that needs to be >>> cleaned up, but I plan on taking care of it soon -- shouldn't be >>> more than a couple of hours to get to basic acceptable behavior. >> Advanced, >>> complex tag searching is a bigger issue that I think is beyond >>> the >> scope >>> of RC2 -- we'll deal with that later. >>> >>> >>> >>> Other Search Object Issues (VUFIND-5, VUFIND-134, VUFIND-145, >>> VUFIND-142): Greg's making pretty steady progress on Search >>> Object changes, and I'm happy to pick up slack if needed. I >>> don't think any >> of >>> the remaining issues are very big -- the hard part is behind us. >>> >>> >>> >>> XSS Issues (VUFIND-54): This issue is never going to totally go >>> away >> -- >>> there will always be chinks in our armor that need patching. >>> We've already fixed many of the most obvious of these problems, >>> and I'll do >> a >>> full review of templates in the next couple of weeks to catch >> remaining >>> problems. No matter how far we get, RC2 will be better than RC1 >>> in >> this >>> regard. >>> >>> >>> >>> RC1 -> RC2 Upgrade Script (VUFIND-132): Till and Greg have >>> already >> done >>> good work on this. I plan on testing it and possibly adding some >>> >> more >>> paranoid error handling when we get closer to RC2 release time. >>> >>> >>> >>> Caching Issues (VUFIND-146): This is a very new issue and already >>> has some comments on it in JIRA -- I expect this will be resolved >>> fairly quickly. >>> >>> >>> >>> EASY TO DEFER FOR 1.0 IF NECESSARY: >>> >>> >>> >>> Finalize Admin Module (VUFIND-10): This is a bonus feature. If >>> we >> can >>> get it done, great. If not, we can turn off the bits that don't >>> work >> yet. >>> >>> >>> SolrMarc Issues (VUFIND-115): The new SolrMarc binary resolves a >> handful >>> of problems noted in JIRA (many not actually scheduled for RC2 >>> release). I'm making good progress on implementing this in my >> branch, >>> so we may be able to merge it into an RC2 release. If that >>> doesn't happen in time, I don't think this is a show-stopper. >>> >>> >>> >>> Advanced Search Limits (VUFIND-139): The most blatant problems >>> here >> are >>> already fixed. The illustration indexing needs some work, and I >>> plan >> on >>> trying to improve it using the scripting capabilities of the new >>> SolrMarc release. If we get the new SolrMarc into RC2, this last >>> >> detail >>> can be fixed in RC2. If we opt not to do that, we're still >>> better >> off >>> than we were in RC1, and we can make deeper improvements later. >>> >>> >>> >>> IE CSS Problems in Browse Mode (VUFIND-91): This is a cosmetic >>> issue that I would like to see fixed... but if we don't get that >>> far, it doesn't impede functionality and it could certainly be >>> worse. >> Haven't >>> heard if Chris Barr is able to devote any time to this, but if he >>> >> isn't, >>> I can look at it. I already decided to just bite the bullet and >>> fix >> the >>> more serious VUFIND-90 CSS problem myself. >>> >>> >>> >>> POSSIBLY ALREADY RESOLVED: >>> >>> >>> >>> Implement 1.0 Default Theme (VUFIND-11): I believe this is done, >>> but >> I >>> haven't closed it since I'm not sure if Andrew's aware of some >> details >>> I'm missing. Any objections to considering this finished at this >>> >> point? >>> >>> >>> File_MARC Exception Problem (VUFIND-6): I'm not sure how to >>> reproduce this or whether it still even applies to our code. >>> Andrew, do you >> know >>> anything about the status? >>> >>> >>> >>> *From:* Andrew Nagy [mailto:as...@gm...] *Sent:* Tuesday, >>> October 27, 2009 11:54 AM *To:* >>> vuf...@li... *Subject:* [Vufind-admins] >>> RC2 Release >>> >>> >>> >>> So - as pointed out by Till in an email on vufind-general, many >>> folks are on RC1 which is becoming very out dated ("obsolete" was >>> Till's word). We still have quite a few major tasks for RC2 >>> release. As >> much >>> as I hate to say it - should we create an RC3 milestone and move >>> some >> of >>> the work that needs more time to RC3 so we can get an RC2 release >>> >> out? >>> I think this might also help buy some credibility from the >>> library community since VuFind has not seen a release in a long >>> time. >>> >>> Thoughts? >>> >>> Andrew >>> >>> >>> --------------------------------------------------------------------- >>> >> --- >>> --------------------------------------------------------------------- >>> >> --------- >>> Come build with us! The BlackBerry(R) Developer Conference in SF, >>> CA is the only developer event you need to attend this year. >>> Jumpstart >> your >>> developing skills, take BlackBerry mobile applications to market >>> and >> stay >>> ahead of the curve. Join us from November 9 - 12, 2009. Register >>> now! http://p.sf.net/sfu/devconference >>> >>> >>> --------------------------------------------------------------------- >>> >> --- >>> _______________________________________________ Vufind-admins >>> mailing list Vuf...@li... >>> https://lists.sourceforge.net/lists/listinfo/vufind-admins > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your developing skills, take BlackBerry mobile applications to market > and stay ahead of the curve. Join us from November 9 - 12, 2009. > Register now! http://p.sf.net/sfu/devconference > _______________________________________________ Vufind-admins mailing > list Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-admins > |
From: Demian K. <dem...@vi...> - 2009-10-27 18:41:01
|
To answer your questions: 1.) I personally agree that it's probably better to get the new SolrMarc into RC2 rather than waiting until 1.0. I think there's a pretty good chance that this will happen. However, it'll take some testing and an admin vote to be totally sure of that. I'm hoping to make more progress on the issue later this afternoon, since I just got the answers I needed from the ever-helpful Bob Haschert. 2.) The purpose of RC2 is to get a stable release out there as quickly as possible -- we're focusing entirely on bug fixes and ignoring new features in the interest of getting it done. Dewey support is important, but I assigned it to 1.0 rather than RC2 because it's not a requirement for making a new working release that maintains the existing functionality of previous releases. I don't want to speculate on a release date for 1.0 since we haven't set one for RC2 yet. However, building very basic Dewey support on top of RC2 is probably not going to be too monstrous of a project. Regardless of the 1.0 release date, I think we can have something working for you very shortly after RC2 is released (maybe sooner, if the SolrMarc upgrade goes to the trunk quickly). The best approach may be to set up a Dewey development branch in Subversion. I can install my work so far there, and then Lehigh (and any other interested Dewey institutions) can install from that branch, test, and contribute improvements. When everyone is satisfied with it, we can merge it back into the trunk for inclusion in 1.0. Let me know if this sounds reasonable; if so, I can set it up as soon as the SolrMarc upgrade is complete. It's certainly worth a few minutes of my time to establish a branch and commit my work so far if it lets you start putting things in motion on your end. - Demian > -----Original Message----- > From: Tim McGeary [mailto:tim.mcgeary@Lehigh.EDU] > Sent: Tuesday, October 27, 2009 2:11 PM > To: Demian Katz > Cc: vuf...@li... > Subject: Re: [Vufind-admins] RC2 Release > > Two follow-up questions: > > 1.) Is it wise to make a SolrMarc upgrade between RC2 and 1.0? > > 2.) I'm a little nervous about waiting for 1.0 to release support for a > call number classification that is still the most used classification > in > the world. > > Forgive me if I've missed this (I'm behind in all of the mailing > lists), > but what is your goal for the date of the 1.0 release? > > At this point, that is the major piece that we need to put VuFind in > production. Everything else is gravy. Once that is in place, I can > put > resources into VuFind. > > Tim > > > Tim McGeary > Team Leader, Library Technology > Lehigh University > 610-758-4998 > tim...@le... > GTalk/Yahoo/Skype: timmcgeary > > > Demian Katz wrote: > > Right now, Dewey is on the 1.0 list rather than the RC2 list. > > Realistically speaking, its implementation largely hinges on the > > SolrMarc upgrade I mention near VUFIND-115 below. Once we upgrade to > > the new SolrMarc, plugging in the necessary Dewey functionality will > > be much easier thanks to its support for writing custom external > > indexing scripts without recompiling the whole SolrMarc application. > > I'm currently working on the upgrade in the demian_solrmarc branch > > under SVN -- it's just about working, but I'm waiting for feedback > > from Bob Haschart about a couple of minor problems. Once those are > > addressed, I'll post more information to the vufind-tech list so we > > can move forward on testing and eventual reintegration with the > > trunk. Once the trunk is upgraded, the Dewey work I shared with you > > a few weeks ago can be easily incorporated into VuFind. > > > > - Demian > > > >> -----Original Message----- From: Tim McGeary > >> [mailto:tmm8@Lehigh.EDU] Sent: Tuesday, October 27, 2009 1:02 PM > >> To: Demian Katz Cc: Andrew Nagy; > >> vuf...@li... Subject: Re: [Vufind-admins] > >> RC2 Release > >> > >> Where does support for Dewey call numbering fit into the list > >> below? > >> > >> Tim > >> > >> Tim McGeary Team Leader, Library Technology Lehigh University > >> 610-758-4998 tim...@le... GTalk/Yahoo/Skype: timmcgeary > >> > >> > >> Demian Katz wrote: > >>> Personally, I don't think an RC3 milestone is necessary -- I'd be > >>> > >> more > >>> inclined to shift more items from RC2 to 1.0 if we feel we > >>> absolutely can't get everything done in time. I also don't think > >>> the remaining > >> RC2 > >>> tasks are necessarily all that major. > >>> > >>> > >>> > >>> I've been on the verge of sending an email proposing that we set > >>> an official release date for RC2 -- I guess now is as good a time > >>> as any > >> to > >>> start that discussion. I personally think we should have > >>> something releasable by the end of the year, so a mid-December > >>> date might be reasonable. Honestly, I think the current trunk > >>> has already reached > >> the > >>> point where it's superior to RC1 even with a few known problems. > >>> > >>> > >>> > >>> To back up my "by the end of the year" proposal, the bottom of > >>> this email contains my thoughts on the remaining JIRA issues, > >>> grouped into clusters. Am I missing anything? Does anyone feel > >>> more pessimistic than I do? > >>> > >>> > >>> > >>> One other thought -- if there's anybody on the list who hasn't > >>> been working with the latest trunk code, now would be a good time > >>> to start > >> if > >>> you have the time. It would be helpful to have some fresh eyes > >>> on > >> this > >>> to catch any new issues that the rest of us have missed. > >>> > >>> > >>> > >>> thanks, > >>> > >>> Demian > >>> > >>> > >>> > >>> WORK DEFINITELY NEEDED: > >>> > >>> > >>> > >>> Tag search consistency (VUFIND-106): Greg has already improved > >>> this > >> with > >>> the Search Object. There's still some weirdness that needs to be > >>> cleaned up, but I plan on taking care of it soon -- shouldn't be > >>> more than a couple of hours to get to basic acceptable behavior. > >> Advanced, > >>> complex tag searching is a bigger issue that I think is beyond > >>> the > >> scope > >>> of RC2 -- we'll deal with that later. > >>> > >>> > >>> > >>> Other Search Object Issues (VUFIND-5, VUFIND-134, VUFIND-145, > >>> VUFIND-142): Greg's making pretty steady progress on Search > >>> Object changes, and I'm happy to pick up slack if needed. I > >>> don't think any > >> of > >>> the remaining issues are very big -- the hard part is behind us. > >>> > >>> > >>> > >>> XSS Issues (VUFIND-54): This issue is never going to totally go > >>> away > >> -- > >>> there will always be chinks in our armor that need patching. > >>> We've already fixed many of the most obvious of these problems, > >>> and I'll do > >> a > >>> full review of templates in the next couple of weeks to catch > >> remaining > >>> problems. No matter how far we get, RC2 will be better than RC1 > >>> in > >> this > >>> regard. > >>> > >>> > >>> > >>> RC1 -> RC2 Upgrade Script (VUFIND-132): Till and Greg have > >>> already > >> done > >>> good work on this. I plan on testing it and possibly adding some > >>> > >> more > >>> paranoid error handling when we get closer to RC2 release time. > >>> > >>> > >>> > >>> Caching Issues (VUFIND-146): This is a very new issue and already > >>> has some comments on it in JIRA -- I expect this will be resolved > >>> fairly quickly. > >>> > >>> > >>> > >>> EASY TO DEFER FOR 1.0 IF NECESSARY: > >>> > >>> > >>> > >>> Finalize Admin Module (VUFIND-10): This is a bonus feature. If > >>> we > >> can > >>> get it done, great. If not, we can turn off the bits that don't > >>> work > >> yet. > >>> > >>> > >>> SolrMarc Issues (VUFIND-115): The new SolrMarc binary resolves a > >> handful > >>> of problems noted in JIRA (many not actually scheduled for RC2 > >>> release). I'm making good progress on implementing this in my > >> branch, > >>> so we may be able to merge it into an RC2 release. If that > >>> doesn't happen in time, I don't think this is a show-stopper. > >>> > >>> > >>> > >>> Advanced Search Limits (VUFIND-139): The most blatant problems > >>> here > >> are > >>> already fixed. The illustration indexing needs some work, and I > >>> plan > >> on > >>> trying to improve it using the scripting capabilities of the new > >>> SolrMarc release. If we get the new SolrMarc into RC2, this last > >>> > >> detail > >>> can be fixed in RC2. If we opt not to do that, we're still > >>> better > >> off > >>> than we were in RC1, and we can make deeper improvements later. > >>> > >>> > >>> > >>> IE CSS Problems in Browse Mode (VUFIND-91): This is a cosmetic > >>> issue that I would like to see fixed... but if we don't get that > >>> far, it doesn't impede functionality and it could certainly be > >>> worse. > >> Haven't > >>> heard if Chris Barr is able to devote any time to this, but if he > >>> > >> isn't, > >>> I can look at it. I already decided to just bite the bullet and > >>> fix > >> the > >>> more serious VUFIND-90 CSS problem myself. > >>> > >>> > >>> > >>> POSSIBLY ALREADY RESOLVED: > >>> > >>> > >>> > >>> Implement 1.0 Default Theme (VUFIND-11): I believe this is done, > >>> but > >> I > >>> haven't closed it since I'm not sure if Andrew's aware of some > >> details > >>> I'm missing. Any objections to considering this finished at this > >>> > >> point? > >>> > >>> > >>> File_MARC Exception Problem (VUFIND-6): I'm not sure how to > >>> reproduce this or whether it still even applies to our code. > >>> Andrew, do you > >> know > >>> anything about the status? > >>> > >>> > >>> > >>> *From:* Andrew Nagy [mailto:as...@gm...] *Sent:* Tuesday, > >>> October 27, 2009 11:54 AM *To:* > >>> vuf...@li... *Subject:* [Vufind-admins] > >>> RC2 Release > >>> > >>> > >>> > >>> So - as pointed out by Till in an email on vufind-general, many > >>> folks are on RC1 which is becoming very out dated ("obsolete" was > >>> Till's word). We still have quite a few major tasks for RC2 > >>> release. As > >> much > >>> as I hate to say it - should we create an RC3 milestone and move > >>> some > >> of > >>> the work that needs more time to RC3 so we can get an RC2 release > >>> > >> out? > >>> I think this might also help buy some credibility from the > >>> library community since VuFind has not seen a release in a long > >>> time. > >>> > >>> Thoughts? > >>> > >>> Andrew > >>> > >>> > >>> ------------------------------------------------------------------- > -- > >>> > >> --- > >>> ------------------------------------------------------------------- > -- > >>> > >> --------- > >>> Come build with us! The BlackBerry(R) Developer Conference in SF, > >>> CA is the only developer event you need to attend this year. > >>> Jumpstart > >> your > >>> developing skills, take BlackBerry mobile applications to market > >>> and > >> stay > >>> ahead of the curve. Join us from November 9 - 12, 2009. Register > >>> now! http://p.sf.net/sfu/devconference > >>> > >>> > >>> ------------------------------------------------------------------- > -- > >>> > >> --- > >>> _______________________________________________ Vufind-admins > >>> mailing list Vuf...@li... > >>> https://lists.sourceforge.net/lists/listinfo/vufind-admins > > > > > > --------------------------------------------------------------------- > --------- > > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > > is the only developer event you need to attend this year. Jumpstart > > your developing skills, take BlackBerry mobile applications to market > > and stay ahead of the curve. Join us from November 9 - 12, 2009. > > Register now! http://p.sf.net/sfu/devconference > > _______________________________________________ Vufind-admins mailing > > list Vuf...@li... > > https://lists.sourceforge.net/lists/listinfo/vufind-admins > > |
From: Tim M. <tmm8@Lehigh.EDU> - 2009-10-27 19:41:47
|
I think a Dewey trunk sounds good, and doing it after RC2 rolls out with improved SolrMarc is a good time frame. To be realistic, I'll be hiring a programmer to work on the Kuali OLE Project, and don't have anyone who can offer serious programming skills until the beginning of the new year. I can offer some testing and configuration assistance, but shouldn't be looked at for programming chops. I just don't have to time to keep those skills in practice anymore. Tim Tim McGeary Team Leader, Library Technology Lehigh University 610-758-4998 tim...@le... GTalk/Yahoo/Skype: timmcgeary Demian Katz wrote: > To answer your questions: > > 1.) I personally agree that it's probably better to get the new > SolrMarc into RC2 rather than waiting until 1.0. I think there's a > pretty good chance that this will happen. However, it'll take some > testing and an admin vote to be totally sure of that. I'm hoping to > make more progress on the issue later this afternoon, since I just > got the answers I needed from the ever-helpful Bob Haschert. > > 2.) The purpose of RC2 is to get a stable release out there as > quickly as possible -- we're focusing entirely on bug fixes and > ignoring new features in the interest of getting it done. Dewey > support is important, but I assigned it to 1.0 rather than RC2 > because it's not a requirement for making a new working release that > maintains the existing functionality of previous releases. > > I don't want to speculate on a release date for 1.0 since we haven't > set one for RC2 yet. However, building very basic Dewey support on > top of RC2 is probably not going to be too monstrous of a project. > Regardless of the 1.0 release date, I think we can have something > working for you very shortly after RC2 is released (maybe sooner, if > the SolrMarc upgrade goes to the trunk quickly). > > The best approach may be to set up a Dewey development branch in > Subversion. I can install my work so far there, and then Lehigh (and > any other interested Dewey institutions) can install from that > branch, test, and contribute improvements. When everyone is > satisfied with it, we can merge it back into the trunk for inclusion > in 1.0. Let me know if this sounds reasonable; if so, I can set it > up as soon as the SolrMarc upgrade is complete. It's certainly worth > a few minutes of my time to establish a branch and commit my work so > far if it lets you start putting things in motion on your end. > > - Demian > >> -----Original Message----- From: Tim McGeary >> [mailto:tim.mcgeary@Lehigh.EDU] Sent: Tuesday, October 27, 2009 >> 2:11 PM To: Demian Katz Cc: vuf...@li... >> Subject: Re: [Vufind-admins] RC2 Release >> >> Two follow-up questions: >> >> 1.) Is it wise to make a SolrMarc upgrade between RC2 and 1.0? >> >> 2.) I'm a little nervous about waiting for 1.0 to release support >> for a call number classification that is still the most used >> classification in the world. >> >> Forgive me if I've missed this (I'm behind in all of the mailing >> lists), but what is your goal for the date of the 1.0 release? >> >> At this point, that is the major piece that we need to put VuFind >> in production. Everything else is gravy. Once that is in place, I >> can put resources into VuFind. >> >> Tim >> >> >> Tim McGeary Team Leader, Library Technology Lehigh University >> 610-758-4998 tim...@le... GTalk/Yahoo/Skype: timmcgeary >> >> >> Demian Katz wrote: >>> Right now, Dewey is on the 1.0 list rather than the RC2 list. >>> Realistically speaking, its implementation largely hinges on the >>> SolrMarc upgrade I mention near VUFIND-115 below. Once we >>> upgrade to the new SolrMarc, plugging in the necessary Dewey >>> functionality will be much easier thanks to its support for >>> writing custom external indexing scripts without recompiling the >>> whole SolrMarc application. I'm currently working on the upgrade >>> in the demian_solrmarc branch under SVN -- it's just about >>> working, but I'm waiting for feedback from Bob Haschart about a >>> couple of minor problems. Once those are addressed, I'll post >>> more information to the vufind-tech list so we can move forward >>> on testing and eventual reintegration with the trunk. Once the >>> trunk is upgraded, the Dewey work I shared with you a few weeks >>> ago can be easily incorporated into VuFind. >>> >>> - Demian >>> >>>> -----Original Message----- From: Tim McGeary >>>> [mailto:tmm8@Lehigh.EDU] Sent: Tuesday, October 27, 2009 1:02 >>>> PM To: Demian Katz Cc: Andrew Nagy; >>>> vuf...@li... Subject: Re: >>>> [Vufind-admins] RC2 Release >>>> >>>> Where does support for Dewey call numbering fit into the list >>>> below? >>>> >>>> Tim >>>> >>>> Tim McGeary Team Leader, Library Technology Lehigh University >>>> 610-758-4998 tim...@le... GTalk/Yahoo/Skype: >>>> timmcgeary >>>> >>>> >>>> Demian Katz wrote: >>>>> Personally, I don't think an RC3 milestone is necessary -- >>>>> I'd be >>>>> >>>> more >>>>> inclined to shift more items from RC2 to 1.0 if we feel we >>>>> absolutely can't get everything done in time. I also don't >>>>> think the remaining >>>> RC2 >>>>> tasks are necessarily all that major. >>>>> >>>>> >>>>> >>>>> I've been on the verge of sending an email proposing that we >>>>> set an official release date for RC2 -- I guess now is as >>>>> good a time as any >>>> to >>>>> start that discussion. I personally think we should have >>>>> something releasable by the end of the year, so a >>>>> mid-December date might be reasonable. Honestly, I think the >>>>> current trunk has already reached >>>> the >>>>> point where it's superior to RC1 even with a few known >>>>> problems. >>>>> >>>>> >>>>> >>>>> To back up my "by the end of the year" proposal, the bottom >>>>> of this email contains my thoughts on the remaining JIRA >>>>> issues, grouped into clusters. Am I missing anything? Does >>>>> anyone feel more pessimistic than I do? >>>>> >>>>> >>>>> >>>>> One other thought -- if there's anybody on the list who >>>>> hasn't been working with the latest trunk code, now would be >>>>> a good time to start >>>> if >>>>> you have the time. It would be helpful to have some fresh >>>>> eyes on >>>> this >>>>> to catch any new issues that the rest of us have missed. >>>>> >>>>> >>>>> >>>>> thanks, >>>>> >>>>> Demian >>>>> >>>>> >>>>> >>>>> WORK DEFINITELY NEEDED: >>>>> >>>>> >>>>> >>>>> Tag search consistency (VUFIND-106): Greg has already >>>>> improved this >>>> with >>>>> the Search Object. There's still some weirdness that needs >>>>> to be cleaned up, but I plan on taking care of it soon -- >>>>> shouldn't be more than a couple of hours to get to basic >>>>> acceptable behavior. >>>> Advanced, >>>>> complex tag searching is a bigger issue that I think is >>>>> beyond the >>>> scope >>>>> of RC2 -- we'll deal with that later. >>>>> >>>>> >>>>> >>>>> Other Search Object Issues (VUFIND-5, VUFIND-134, VUFIND-145, >>>>> VUFIND-142): Greg's making pretty steady progress on Search >>>>> Object changes, and I'm happy to pick up slack if needed. I >>>>> don't think any >>>> of >>>>> the remaining issues are very big -- the hard part is behind >>>>> us. >>>>> >>>>> >>>>> >>>>> XSS Issues (VUFIND-54): This issue is never going to totally >>>>> go away >>>> -- >>>>> there will always be chinks in our armor that need patching. >>>>> We've already fixed many of the most obvious of these >>>>> problems, and I'll do >>>> a >>>>> full review of templates in the next couple of weeks to catch >>>>> >>>> remaining >>>>> problems. No matter how far we get, RC2 will be better than >>>>> RC1 in >>>> this >>>>> regard. >>>>> >>>>> >>>>> >>>>> RC1 -> RC2 Upgrade Script (VUFIND-132): Till and Greg have >>>>> already >>>> done >>>>> good work on this. I plan on testing it and possibly adding >>>>> some >>>>> >>>> more >>>>> paranoid error handling when we get closer to RC2 release >>>>> time. >>>>> >>>>> >>>>> >>>>> Caching Issues (VUFIND-146): This is a very new issue and >>>>> already has some comments on it in JIRA -- I expect this will >>>>> be resolved fairly quickly. >>>>> >>>>> >>>>> >>>>> EASY TO DEFER FOR 1.0 IF NECESSARY: >>>>> >>>>> >>>>> >>>>> Finalize Admin Module (VUFIND-10): This is a bonus feature. >>>>> If we >>>> can >>>>> get it done, great. If not, we can turn off the bits that >>>>> don't work >>>> yet. >>>>> >>>>> SolrMarc Issues (VUFIND-115): The new SolrMarc binary >>>>> resolves a >>>> handful >>>>> of problems noted in JIRA (many not actually scheduled for >>>>> RC2 release). I'm making good progress on implementing this >>>>> in my >>>> branch, >>>>> so we may be able to merge it into an RC2 release. If that >>>>> doesn't happen in time, I don't think this is a show-stopper. >>>>> >>>>> >>>>> >>>>> >>>>> Advanced Search Limits (VUFIND-139): The most blatant >>>>> problems here >>>> are >>>>> already fixed. The illustration indexing needs some work, >>>>> and I plan >>>> on >>>>> trying to improve it using the scripting capabilities of the >>>>> new SolrMarc release. If we get the new SolrMarc into RC2, >>>>> this last >>>>> >>>> detail >>>>> can be fixed in RC2. If we opt not to do that, we're still >>>>> better >>>> off >>>>> than we were in RC1, and we can make deeper improvements >>>>> later. >>>>> >>>>> >>>>> >>>>> IE CSS Problems in Browse Mode (VUFIND-91): This is a >>>>> cosmetic issue that I would like to see fixed... but if we >>>>> don't get that far, it doesn't impede functionality and it >>>>> could certainly be worse. >>>> Haven't >>>>> heard if Chris Barr is able to devote any time to this, but >>>>> if he >>>>> >>>> isn't, >>>>> I can look at it. I already decided to just bite the bullet >>>>> and fix >>>> the >>>>> more serious VUFIND-90 CSS problem myself. >>>>> >>>>> >>>>> >>>>> POSSIBLY ALREADY RESOLVED: >>>>> >>>>> >>>>> >>>>> Implement 1.0 Default Theme (VUFIND-11): I believe this is >>>>> done, but >>>> I >>>>> haven't closed it since I'm not sure if Andrew's aware of >>>>> some >>>> details >>>>> I'm missing. Any objections to considering this finished at >>>>> this >>>>> >>>> point? >>>>> >>>>> File_MARC Exception Problem (VUFIND-6): I'm not sure how to >>>>> reproduce this or whether it still even applies to our code. >>>>> Andrew, do you >>>> know >>>>> anything about the status? >>>>> >>>>> >>>>> >>>>> *From:* Andrew Nagy [mailto:as...@gm...] *Sent:* >>>>> Tuesday, October 27, 2009 11:54 AM *To:* >>>>> vuf...@li... *Subject:* >>>>> [Vufind-admins] RC2 Release >>>>> >>>>> >>>>> >>>>> So - as pointed out by Till in an email on vufind-general, >>>>> many folks are on RC1 which is becoming very out dated >>>>> ("obsolete" was Till's word). We still have quite a few >>>>> major tasks for RC2 release. As >>>> much >>>>> as I hate to say it - should we create an RC3 milestone and >>>>> move some >>>> of >>>>> the work that needs more time to RC3 so we can get an RC2 >>>>> release >>>>> >>>> out? >>>>> I think this might also help buy some credibility from the >>>>> library community since VuFind has not seen a release in a >>>>> long time. >>>>> >>>>> Thoughts? >>>>> >>>>> Andrew >>>>> >>>>> >>>>> ------------------------------------------------------------------- >>>>> >> -- >>>> --- >>>>> ------------------------------------------------------------------- >>>>> >> -- >>>> --------- >>>>> Come build with us! The BlackBerry(R) Developer Conference in >>>>> SF, CA is the only developer event you need to attend this >>>>> year. Jumpstart >>>> your >>>>> developing skills, take BlackBerry mobile applications to >>>>> market and >>>> stay >>>>> ahead of the curve. Join us from November 9 - 12, 2009. >>>>> Register now! http://p.sf.net/sfu/devconference >>>>> >>>>> >>>>> ------------------------------------------------------------------- >>>>> >> -- >>>> --- >>>>> _______________________________________________ Vufind-admins >>>>> mailing list Vuf...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/vufind-admins >>> >>> --------------------------------------------------------------------- >>> >> --------- >>> Come build with us! The BlackBerry(R) Developer Conference in SF, >>> CA is the only developer event you need to attend this year. >>> Jumpstart your developing skills, take BlackBerry mobile >>> applications to market and stay ahead of the curve. Join us from >>> November 9 - 12, 2009. Register now! >>> http://p.sf.net/sfu/devconference >>> _______________________________________________ Vufind-admins >>> mailing list Vuf...@li... >>> https://lists.sourceforge.net/lists/listinfo/vufind-admins >>> > |
From: Osullivan L. <L.O...@sw...> - 2009-10-28 11:08:44
|
Hi Demian, With regards to Tags (and comments), a pretty crucial option for me is going to be the ability to turn them on or off. Without any form of moderation, I'm pretty sure that it wouldn't take our students long to have all sorts of messages appearing on screen! Where do you think this issue stands? Cheers, Luke ________________________________ From: Demian Katz [mailto:dem...@vi...] Sent: 27 October 2009 16:36 To: Andrew Nagy; vuf...@li... Subject: Re: [Vufind-admins] RC2 Release Personally, I don't think an RC3 milestone is necessary -- I'd be more inclined to shift more items from RC2 to 1.0 if we feel we absolutely can't get everything done in time. I also don't think the remaining RC2 tasks are necessarily all that major. I've been on the verge of sending an email proposing that we set an official release date for RC2 -- I guess now is as good a time as any to start that discussion. I personally think we should have something releasable by the end of the year, so a mid-December date might be reasonable. Honestly, I think the current trunk has already reached the point where it's superior to RC1 even with a few known problems. To back up my "by the end of the year" proposal, the bottom of this email contains my thoughts on the remaining JIRA issues, grouped into clusters. Am I missing anything? Does anyone feel more pessimistic than I do? One other thought -- if there's anybody on the list who hasn't been working with the latest trunk code, now would be a good time to start if you have the time. It would be helpful to have some fresh eyes on this to catch any new issues that the rest of us have missed. thanks, Demian WORK DEFINITELY NEEDED: Tag search consistency (VUFIND-106): Greg has already improved this with the Search Object. There's still some weirdness that needs to be cleaned up, but I plan on taking care of it soon -- shouldn't be more than a couple of hours to get to basic acceptable behavior. Advanced, complex tag searching is a bigger issue that I think is beyond the scope of RC2 -- we'll deal with that later. Other Search Object Issues (VUFIND-5, VUFIND-134, VUFIND-145, VUFIND-142): Greg's making pretty steady progress on Search Object changes, and I'm happy to pick up slack if needed. I don't think any of the remaining issues are very big -- the hard part is behind us. XSS Issues (VUFIND-54): This issue is never going to totally go away -- there will always be chinks in our armor that need patching. We've already fixed many of the most obvious of these problems, and I'll do a full review of templates in the next couple of weeks to catch remaining problems. No matter how far we get, RC2 will be better than RC1 in this regard. RC1 -> RC2 Upgrade Script (VUFIND-132): Till and Greg have already done good work on this. I plan on testing it and possibly adding some more paranoid error handling when we get closer to RC2 release time. Caching Issues (VUFIND-146): This is a very new issue and already has some comments on it in JIRA -- I expect this will be resolved fairly quickly. EASY TO DEFER FOR 1.0 IF NECESSARY: Finalize Admin Module (VUFIND-10): This is a bonus feature. If we can get it done, great. If not, we can turn off the bits that don't work yet. SolrMarc Issues (VUFIND-115): The new SolrMarc binary resolves a handful of problems noted in JIRA (many not actually scheduled for RC2 release). I'm making good progress on implementing this in my branch, so we may be able to merge it into an RC2 release. If that doesn't happen in time, I don't think this is a show-stopper. Advanced Search Limits (VUFIND-139): The most blatant problems here are already fixed. The illustration indexing needs some work, and I plan on trying to improve it using the scripting capabilities of the new SolrMarc release. If we get the new SolrMarc into RC2, this last detail can be fixed in RC2. If we opt not to do that, we're still better off than we were in RC1, and we can make deeper improvements later. IE CSS Problems in Browse Mode (VUFIND-91): This is a cosmetic issue that I would like to see fixed... but if we don't get that far, it doesn't impede functionality and it could certainly be worse. Haven't heard if Chris Barr is able to devote any time to this, but if he isn't, I can look at it. I already decided to just bite the bullet and fix the more serious VUFIND-90 CSS problem myself. POSSIBLY ALREADY RESOLVED: Implement 1.0 Default Theme (VUFIND-11): I believe this is done, but I haven't closed it since I'm not sure if Andrew's aware of some details I'm missing. Any objections to considering this finished at this point? File_MARC Exception Problem (VUFIND-6): I'm not sure how to reproduce this or whether it still even applies to our code. Andrew, do you know anything about the status? From: Andrew Nagy [mailto:as...@gm...] Sent: Tuesday, October 27, 2009 11:54 AM To: vuf...@li... Subject: [Vufind-admins] RC2 Release So - as pointed out by Till in an email on vufind-general, many folks are on RC1 which is becoming very out dated ("obsolete" was Till's word). We still have quite a few major tasks for RC2 release. As much as I hate to say it - should we create an RC3 milestone and move some of the work that needs more time to RC3 so we can get an RC2 release out? I think this might also help buy some credibility from the library community since VuFind has not seen a release in a long time. Thoughts? Andrew |
From: Demian K. <dem...@vi...> - 2009-10-28 13:03:20
|
I see you've already got this issue in JIRA as VUFIND-135 -- I've just renamed the issue to expand the scope. It's currently scheduled as a "wishlist" issue, but it sounds like a reasonable candidate for inclusion in 1.0. Since it's on the "useful but non-essential" list, I wouldn't expect it in RC2. Feel free to point this out on the vufind-tech list so we can discuss the best implementation strategy. I've added a comment in JIRA with one proposed approach. If we can agree on the details, I don't think it should take too long to write the code to make it happen. - Demian From: Osullivan L. [mailto:L.O...@sw...] Sent: Wednesday, October 28, 2009 7:08 AM To: Demian Katz; Andrew Nagy; vuf...@li... Subject: RE: [Vufind-admins] RC2 Release Hi Demian, With regards to Tags (and comments), a pretty crucial option for me is going to be the ability to turn them on or off. Without any form of moderation, I'm pretty sure that it wouldn't take our students long to have all sorts of messages appearing on screen! Where do you think this issue stands? Cheers, Luke ________________________________ From: Demian Katz [mailto:dem...@vi...] Sent: 27 October 2009 16:36 To: Andrew Nagy; vuf...@li... Subject: Re: [Vufind-admins] RC2 Release Personally, I don't think an RC3 milestone is necessary -- I'd be more inclined to shift more items from RC2 to 1.0 if we feel we absolutely can't get everything done in time. I also don't think the remaining RC2 tasks are necessarily all that major. I've been on the verge of sending an email proposing that we set an official release date for RC2 -- I guess now is as good a time as any to start that discussion. I personally think we should have something releasable by the end of the year, so a mid-December date might be reasonable. Honestly, I think the current trunk has already reached the point where it's superior to RC1 even with a few known problems. To back up my "by the end of the year" proposal, the bottom of this email contains my thoughts on the remaining JIRA issues, grouped into clusters. Am I missing anything? Does anyone feel more pessimistic than I do? One other thought -- if there's anybody on the list who hasn't been working with the latest trunk code, now would be a good time to start if you have the time. It would be helpful to have some fresh eyes on this to catch any new issues that the rest of us have missed. thanks, Demian WORK DEFINITELY NEEDED: Tag search consistency (VUFIND-106): Greg has already improved this with the Search Object. There's still some weirdness that needs to be cleaned up, but I plan on taking care of it soon -- shouldn't be more than a couple of hours to get to basic acceptable behavior. Advanced, complex tag searching is a bigger issue that I think is beyond the scope of RC2 -- we'll deal with that later. Other Search Object Issues (VUFIND-5, VUFIND-134, VUFIND-145, VUFIND-142): Greg's making pretty steady progress on Search Object changes, and I'm happy to pick up slack if needed. I don't think any of the remaining issues are very big -- the hard part is behind us. XSS Issues (VUFIND-54): This issue is never going to totally go away -- there will always be chinks in our armor that need patching. We've already fixed many of the most obvious of these problems, and I'll do a full review of templates in the next couple of weeks to catch remaining problems. No matter how far we get, RC2 will be better than RC1 in this regard. RC1 -> RC2 Upgrade Script (VUFIND-132): Till and Greg have already done good work on this. I plan on testing it and possibly adding some more paranoid error handling when we get closer to RC2 release time. Caching Issues (VUFIND-146): This is a very new issue and already has some comments on it in JIRA -- I expect this will be resolved fairly quickly. EASY TO DEFER FOR 1.0 IF NECESSARY: Finalize Admin Module (VUFIND-10): This is a bonus feature. If we can get it done, great. If not, we can turn off the bits that don't work yet. SolrMarc Issues (VUFIND-115): The new SolrMarc binary resolves a handful of problems noted in JIRA (many not actually scheduled for RC2 release). I'm making good progress on implementing this in my branch, so we may be able to merge it into an RC2 release. If that doesn't happen in time, I don't think this is a show-stopper. Advanced Search Limits (VUFIND-139): The most blatant problems here are already fixed. The illustration indexing needs some work, and I plan on trying to improve it using the scripting capabilities of the new SolrMarc release. If we get the new SolrMarc into RC2, this last detail can be fixed in RC2. If we opt not to do that, we're still better off than we were in RC1, and we can make deeper improvements later. IE CSS Problems in Browse Mode (VUFIND-91): This is a cosmetic issue that I would like to see fixed... but if we don't get that far, it doesn't impede functionality and it could certainly be worse. Haven't heard if Chris Barr is able to devote any time to this, but if he isn't, I can look at it. I already decided to just bite the bullet and fix the more serious VUFIND-90 CSS problem myself. POSSIBLY ALREADY RESOLVED: Implement 1.0 Default Theme (VUFIND-11): I believe this is done, but I haven't closed it since I'm not sure if Andrew's aware of some details I'm missing. Any objections to considering this finished at this point? File_MARC Exception Problem (VUFIND-6): I'm not sure how to reproduce this or whether it still even applies to our code. Andrew, do you know anything about the status? From: Andrew Nagy [mailto:as...@gm...] Sent: Tuesday, October 27, 2009 11:54 AM To: vuf...@li... Subject: [Vufind-admins] RC2 Release So - as pointed out by Till in an email on vufind-general, many folks are on RC1 which is becoming very out dated ("obsolete" was Till's word). We still have quite a few major tasks for RC2 release. As much as I hate to say it - should we create an RC3 milestone and move some of the work that needs more time to RC3 so we can get an RC2 release out? I think this might also help buy some credibility from the library community since VuFind has not seen a release in a long time. Thoughts? Andrew |