metaperl has asked for the wisdom of the Perl Monks concerning the following question:
Due to time constraints at work, I will be applying patches to DBIx::Simple in order to address a bug which directly affects some commercial software I am developing.
I have imported the CPAN sources for DBIx::Simple and plan to patch in a systematic fashion so Juerd can follow them and perhaps apply them to his distro. I thought of contacting the various people that have submitted bugs and solicit patches but I'm not sure if that's spamming them.
One change from DBIx::Simple that I'm excited about is replacing SQL::Abstract with SQL::Abstract::More so that I can take advantage of its expanded query-generation power, which includes a join syntax!
So for the time being, I suppose I will just develop and patch at github and use my forked version in our production software for a few months and document each change thoroughly. Any feedback on the proper way to handle forking this module is appreciated.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: How should a fork of DBIx::Simple be handled?
by Juerd (Abbot) on Aug 30, 2011 at 16:55 UTC | |
by Anonymous Monk on Aug 31, 2011 at 03:34 UTC | |
by Corion (Patriarch) on Aug 31, 2011 at 05:31 UTC | |
by metaperl (Curate) on Aug 31, 2011 at 11:22 UTC | |
by tye (Sage) on Aug 31, 2011 at 13:52 UTC | |
| |
|