[ https://issues.apache.org/jira/browse/SOLR-13952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16980773#comment-16980773
]
David Smiley commented on SOLR-13952:
-------------------------------------
Then file an issue RE SuppressWarnings with 200 files and commit that. That's a valid subject/theme
that could have a commit message that makes sense. I just don't want a commit/issue that's
basically "Bunch of random stuff Mark did; he knows best"
> Separate out Gradle-specific code from other (mostly test) changes and commit separately
> ----------------------------------------------------------------------------------------
>
> Key: SOLR-13952
> URL: https://issues.apache.org/jira/browse/SOLR-13952
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Major
> Attachments: fordavid.patch
>
>
> The gradle_8 branch has many changes unrelated to gradle. It would be much easier to
work on the gradle parts if these were separated. So here's my plan:
> - establish a branch to use for the non-gradle parts of the gradle_8 branch and commit
separately. For a first cut, I'll make all the changes I'm confident of, and mark the others
with nocommits so we can iterate and decide when to merge to master and 8x.
> - create a "gradle_9" branch that hosts only the gradle changes for us all to iterate
on.
> I hope to have a preliminary cut at this over the weekend.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
|