[
https://issues.apache.org/jira/browse/OFBIZ-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223694#comment-16223694 ]
Michael Brohl commented on OFBIZ-9902:
--------------------------------------
There are some SQL migration scripts also so I don't see a clear priviligation of services of SQL?
The contents I see there are matching the idea of the changelog very well. It's in historial order so that a user can "replay" all changes as provided in the list in correct order. I agree with Sharan's comment there that we should provide not only the data and commit of the change but also the release(s).
So if we would take this structure, add the missing informations and put it in the document Aditya provided, we would have a good start.
> Create a DATAMODELCHANGES.md to track data model changes
> --------------------------------------------------------
>
> Key: OFBIZ-9902
> URL:
https://issues.apache.org/jira/browse/OFBIZ-9902> Project: OFBiz
> Issue Type: Bug
> Affects Versions: Trunk
> Reporter: Aditya Sharma
> Assignee: Aditya Sharma
> Attachments: DATAMODELCHANGES.md
>
>
> The file will have the format:
> Entity Changes:
> Here we will have a bulleted list with entity names and the revision changes took place
> 1. Added Entities
> 2. Removed Entities
> Field changes:
> Here we will show data in tabular form in format
> entityname | field | action | isPK | revision
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Locked
