If a class name is serialized or used external to the plugin, its super hard to change without breaking compatibility. Generally the initial push is for using facing changes. Text strings, Help files. Docs. Etc
On Tue, Jun 22, 2021 at 6:35 AM 'Fritz Elfert' via Jenkins Developers < [email protected]> wrote: > On 22.06.21 12:01, Oleg Nenashev wrote: > > Hi all, > > > > I am currently updating roadmap and the Jenkins website to reference the > initiative and contributing. > > To group everything and to coordinate contributions, I have created a > Discourse topic here: > https://community.jenkins.io/t/jenkins-terminology-cleanup-initiative-coordination/180 > < > https://community.jenkins.io/t/jenkins-terminology-cleanup-initiative-coordination/180> > . > I will be using it as a main source of contributing guidelines. Please feel > free to contribute! > > What is still unclear to me (asked you in > https://issues.jenkins.io/browse/JENKINS-62833) but no answer yet): > Does this also include java class names or only user-visible > text/messages/doc? > > Thanks > -Fritz > > > > Best regards, > > Oleg Nenashev > > > > On Wednesday, May 19, 2021 at 8:36:41 PM UTC+2 [email protected] > wrote: > > > > On Wed, May 19, 2021 at 8:08 AM 'Gavin Mogan' via Jenkins Developers > <[email protected]> wrote: > > > > I'm actually against updating the changelog. The changes to > terminology were not done then, and by showing the old and the new, you > show growth. I'm not a fan of rewriting history, even in git. > > > > > > We're not "rewriting history" here. You wouldn't leave some wrong > formatting around after migrating a file from Markdown to Asciidoc (or vice > versa). You'd fix old typos. You'd adapt old links when the URL of the > pages they point to change. And if we change the words we use to refer to > something, that applies retroactively as well. > > > > -- > > You received this message because you are subscribed to the Google > Groups "Jenkins Developers" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] <mailto: > [email protected]>. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/bdbaa768-fcf4-45d1-924d-52be07a39c88n%40googlegroups.com > < > https://groups.google.com/d/msgid/jenkinsci-dev/bdbaa768-fcf4-45d1-924d-52be07a39c88n%40googlegroups.com?utm_medium=email&utm_source=footer > >. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/27bb0f2a-5995-d6a2-1f39-11aa1d6670cf%40fritz-elfert.de > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusJ-2QmVF2xsuLRzoFi3GG5KsNtv%3DEz2rBUNCwNbMeb%3DQ%40mail.gmail.com.
