PR #553 factors out some code in the main module into a new method, but doesn’t change the function of it, and is otherwise confined to the JDBCConfig module. Would anyone object to backporting it to 2.5 now rather than waiting a month?
PR #553 factors out some code in the main module into a new method, but doesn’t change the function of it, and is otherwise confined to the JDBCConfig module. Would anyone object to backporting it to 2.5 now rather than waiting a month?
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees
On Thu, Apr 10, 2014 at 10:15 PM, Kevin Smith <ksmith@anonymised.com>wrote:
PR #553 factors out some code in the main module into a new method, but
doesn't change the function of it, and is otherwise confined to the
JDBCConfig module. Would anyone object to backporting it to 2.5 now rather
than waiting a month?
The one month wait is for adding new features, this is mostly a reshuffle
of existing code right?
+1 on backporting
Cheers
Andrea
--
Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
for more information.
Ing. Andrea Aime @geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
+1. Even though it is just a refactoring, backporting code improvements makes later cherry-picking easier.
On 11/04/14 04:15, Kevin Smith wrote:
PR #553 factors out some code in the main module into a new method, but
doesn't change the function of it, and is otherwise confined to the
JDBCConfig module. Would anyone object to backporting it to 2.5 now
rather than waiting a month?
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
+1. Even though it is just a refactoring, backporting code improvements makes later cherry-picking easier.
On 11/04/14 04:15, Kevin Smith wrote:
PR #553 factors out some code in the main module into a new method, but
doesn’t change the function of it, and is otherwise confined to the
JDBCConfig module. Would anyone object to backporting it to 2.5 now
rather than waiting a month?
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees
–
Ben Caradoc-Davies Ben.Caradoc-Davies@anonymised.com
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre