Hi Ben, Rogan, folks, Thanks much for the information and update….this helps! This particular function was used a lot by our libraries in the past, so looking forward to any developments on this one…
--Tony Tony Bandy [email protected]<mailto:[email protected]> OHIONET 1500 West Lane Ave. Columbus, OH 43221-3975 614-486-2966 x19 From: [email protected] [mailto:[email protected]] On Behalf Of Ben Shum Sent: Wednesday, July 16, 2014 2:56 PM To: Evergreen Discussion Group Subject: Re: [OPEN-ILS-GENERAL] Triggered Events Bug #1207533 Hi Tony, Those series targets for 2.4 and 2.5 are there for guidance to developers who might work someday on the bug; by that I mean that the developer who pushes the fix to the master series and backports to supported past versions will update the bug accordingly when that happens. This may mean that a bug status is not continually updated to indicate potential versions that require backport fixing for the bug. The real consequence of not fixing a bug when it's reported immediately reflects as development moves ahead and new versions of Evergreen are released. In most cases, a bug that's first reported to be affecting earlier versions of Evergreen would also continue to affect current and all future versions of Evergreen if not addressed. So a bug reported during 2.4's time and not fixed would continue to be a problem when we release 2.5, 2.6, 2.7, etc. In my opinion, the way Evergreen bugs are supposed to be resolved is to fix it in the master branch and then backport the fix to the past versions as best and timely as possible. With no new information on this particular bug ticket, I would also assume that this issue has yet to be addressed by Evergreen developers with any potential bug fixes and awaits new input / work on that front. That said, I'd love to see this bug fix occur by the time 2.7 comes out and would welcome any patches for review! -- Ben On Wed, Jul 16, 2014 at 2:08 PM, Tony Bandy <[email protected]<mailto:[email protected]>> wrote: Hi all, Maybe I should route this to the dev. list…..but just curious if anyone knows about movement on this bug for Triggered Events: https://bugs.launchpad.net/evergreen/+bug/1207533 I see on the Bugs list that this is only listed as affecting the 2.4.X and 2.5.X series….has this been noted in the 2.7.X builds yet? We really used this feature in 2.3.X and was wondering about it. Thanks for any updates as you have time…. --Tony Tony Bandy [email protected]<mailto:[email protected]> OHIONET 1500 West Lane Ave. Columbus, OH 43221-3975 614-486-2966 x19<tel:614-486-2966%20x19> -- Benjamin Shum Evergreen Systems Manager Bibliomation, Inc. 24 Wooster Ave. Waterbury, CT 06708 203-577-4070, ext. 113
