On Tue, May 29, 2012 at 12:30 PM, Michael Kerrigan <[email protected]> wrote: > Hello Developers, > > We have been hired to customize some of the search functionality for > Evergreen for a client and was hoping someone could point us in the right > direction regarding a couple of issues. > > 1. Should we submit our changes back to the community as a bulk patch > to 2.2 (with all of our changes) or would it be more applicable to submit > each change we are making independently? >
That depends on the features, and their inter-dependence. I would recommend using git topic branches, and not patches, to offer any code. But, note, any feature changes won't be accepted into the core Evergreen 2.2 repository -- for official releases, only git master takes new functionality. > 2. What IDE do you all use for working with and debugging Evergreen > PERL code? Eclipse, Komodo? > Primarily vim with a few folks using emacs. > 3. Who is the resident expert on Evergreen search functionality? > If there was only one slot available then that would nominally be me, I suppose, but others are quite knowledgeable as well so keeping discussions on the list is important. -- Mike Rylander | Director of Research and Development | Equinox Software, Inc. / Your Library's Guide to Open Source | phone: 1-877-OPEN-ILS (673-6457) | email: [email protected] | web: http://www.esilibrary.com
