[wp-meta] [Making WordPress.org] #4252: De-prioritize plugin changelog translation

Making WordPress.org noreply at wordpress.org
Fri Mar 8 11:50:35 UTC 2019

#4252: De-prioritize plugin changelog translation
 Reporter:  Nao                       |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |

Comment (by Luciano Croce):

 @dd32 about the B proposal (separate change log into a sub-project) what
 do you think?

 Could it be a possible change?

 In this case (for example) for plugins you would have three separate


 The current Detailed Plugin Guidelines already recommend to separating the
 change log from the readme.txt (for example) in a separate changelog.txt
 file but this has not yet become a definitive standard.

 For example, I have planned to do it in my plugins, starting from the next
 new versions (taking inspiration from the gutenberg plugin) and leaving
 only the current change log in the readme.txt.

 As a developer, the change log help me to search the features/changes that
 I need for a new plugins or in troubleshooting (for example) but I don't
 think it's at all useful to preserve all old changes since release 0.1
 this is why I believe that the separation can be a useful solution, and
 splitting the whole change log, in my opinion, could be a better solution.

Ticket URL: <https://meta.trac.wordpress.org/ticket/4252#comment:8>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list