[
https://issues.apache.org/jira/browse/TIKA-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146288#comment-17146288
]
Konstantin Gribov commented on TIKA-3121:
-----------------------------------------
I didn't vote before and a bit ambivalent about change. Despite all Rich's
pushing towards renaming I'm a bit concerned about real impact on developer
biased community. For me it looks more like populist decision but I may be
biased by previous hate storms that used D&I ideas against anyone who don't
kneel and plead to spare them despite not being in some minority.
We will have to go through documentation, wiki, configuration for CI etc to
ensure that new branch name is used but we can do this only for our projects.
All external developers who include Tika in their build systems, delivery
pipelines, writes articles/books and using master branch would have to do some
additional (and sometimes unexpected) work. In ideal world it would be done via
usual scripts/configuration maintenance but a lot of thing with low prio
support or without actual maintenance could break.
So, I'm basically -0.5, weak against 'cause potential impact on downstream
users and fellow developers.
> Rename master branch
> --------------------
>
> Key: TIKA-3121
> URL: https://issues.apache.org/jira/browse/TIKA-3121
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
>
> I started a discussion on the dev list for this here:
> http://mail-archives.us.apache.org/mod_mbox/tika-dev/202006.mbox/%3CCAC1dCwW9FuK%2BkSzokmweeYwLFiED9g0W-43J1TNhMwnv7rdp8g%40mail.gmail.com%3E
> One committer would prefer that we not make this change, but seems ok with it.
> Recommendations:
> * main
> * trunk
> * development
> * stable
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
