I know for the svn, it's not the problem.
I prefer keep the deprecated file on branch 14.x and remove them on the
next stable candidate branch.
It leaves the time to production site to adapt their patch.
Nicolas
Le 21/03/2015 00:42, Pierre Smits a écrit :
Nicolas,
Keeping the old file in doesn't exactly make sense. We use SVN to track
changes, and with issues registered in JIRA we can report in an easy manner
what kind of changes are effected in a release.
If we do this in a case-by-case (or per file) way, we make the change
visible. And it will surely come in play when people are considering
upgrading to a new major release.
Please keep in mind, this is an improvement. Thus not intended to go into
releases of current running release branches (12.x, 13,x). It could go in
r14.x, but that is not up to me.
Best regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
Le 21/03/2015 00:42, Pierre Smits a écrit :
Nicolas,
Keeping the old file in doesn't exactly make sense. We use SVN to track
changes, and with issues registered in JIRA we can report in an easy manner
what kind of changes are effected in a release.
If we do this in a case-by-case (or per file) way, we make the change
visible. And it will surely come in play when people are considering
upgrading to a new major release.
Please keep in mind, this is an improvement. Thus not intended to go into
releases of current running release branches (12.x, 13,x). It could go in
r14.x, but that is not up to me.
Best regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
On Fri, Mar 20, 2015 at 9:05 PM, Nicolas Malin <[email protected]>
wrote:
This make sense and I like each element that homogenize OFBiz ;)
But I propose to keep old file with deprecated information.
# Dear developper, this file is now deprecated plus use
component.properties instead of. Own apologies for all inconvenience
Nicolas
Le 20/03/2015 15:03, Pierre Smits a écrit :
The same can be applied to the following .properties files:
- in applications stack
- securityext: truition.properties -> securityext.properties
- workeffort: workeffortsearch.properties -> workeffort.properties
- in special purpose stack
- ebay: ebayExport.properties -> ebay.properties
- ebaystore: EbayStore.properties -> ebaystore.properties
- googlebase: googleBaseExport.properties -> googlebase.properties
- googlecheckout: googleCheckout.properties ->
googlecheckout.properties
- lucene: search.properties -> lucene.properties
- pos: parameters.properties -> pos.properties
- scrum: revision.properties -> scrum.properties
Best regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
Le 21/03/2015 00:42, Pierre Smits a écrit :
Nicolas,
Keeping the old file in doesn't exactly make sense. We use SVN to track
changes, and with issues registered in JIRA we can report in an easy manner
what kind of changes are effected in a release.
If we do this in a case-by-case (or per file) way, we make the change
visible. And it will surely come in play when people are considering
upgrading to a new major release.
Please keep in mind, this is an improvement. Thus not intended to go into
releases of current running release branches (12.x, 13,x). It could go in
r14.x, but that is not up to me.
Best regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
On Fri, Mar 20, 2015 at 9:05 PM, Nicolas Malin <[email protected]>
wrote:
This make sense and I like each element that homogenize OFBiz ;)
But I propose to keep old file with deprecated information.
# Dear developper, this file is now deprecated plus use
component.properties instead of. Own apologies for all inconvenience
Nicolas
Le 20/03/2015 15:03, Pierre Smits a écrit :
The same can be applied to the following .properties files:
- in applications stack
- securityext: truition.properties -> securityext.properties
- workeffort: workeffortsearch.properties -> workeffort.properties
- in special purpose stack
- ebay: ebayExport.properties -> ebay.properties
- ebaystore: EbayStore.properties -> ebaystore.properties
- googlebase: googleBaseExport.properties -> googlebase.properties
- googlecheckout: googleCheckout.properties ->
googlecheckout.properties
- lucene: search.properties -> lucene.properties
- pos: parameters.properties -> pos.properties
- scrum: revision.properties -> scrum.properties
Best regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
http://www.orrtiz.com
On Fri, Mar 20, 2015 at 9:05 PM, Nicolas Malin <[email protected]>
wrote:
This make sense and I like each element that homogenize OFBiz ;)
But I propose to keep old file with deprecated information.
# Dear developper, this file is now deprecated plus use
component.properties instead of. Own apologies for all inconvenience
Nicolas
Le 20/03/2015 15:03, Pierre Smits a écrit :
The same can be applied to the following .properties files:
- in applications stack
- securityext: truition.properties -> securityext.properties
- workeffort: workeffortsearch.properties -> workeffort.properties
- in special purpose stack
- ebay: ebayExport.properties -> ebay.properties
- ebaystore: EbayStore.properties -> ebaystore.properties
- googlebase: googleBaseExport.properties -> googlebase.properties
- googlecheckout: googleCheckout.properties ->
googlecheckout.properties
- lucene: search.properties -> lucene.properties
- pos: parameters.properties -> pos.properties
- scrum: revision.properties -> scrum.properties
Best regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
