Skip to content

Exclude some files from the source release.#4551

Open
dsmiley wants to merge 1 commit into
apache:mainfrom
dsmiley:exclude-AGENTS.md-from-source-release
Open

Exclude some files from the source release.#4551
dsmiley wants to merge 1 commit into
apache:mainfrom
dsmiley:exclude-AGENTS.md-from-source-release

Conversation

@dsmiley

@dsmiley dsmiley commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Thus avoiding ASF requirements for such files to have source headers.

Deferring header removal to a follow-up.

To know if this truly breaks anything, we'll sadly need to wait for the smoketester, as we have no PR invokable smoketest validation workflow/task nor a way to run it locally in my experience. My attempts to run it locally a couple months ago kept turning up one problem after another.

Thus avoiding ASF requirements for such files to have source headers.
@dsmiley dsmiley requested review from gerlowskija and janhoy June 26, 2026 04:40
@dsmiley

dsmiley commented Jun 26, 2026

Copy link
Copy Markdown
Contributor Author

I could remove some headers here as well... but that snowballs to manipulating RAT config... well okay I could.

Ideally IMO RAT runs at smoketester phase.

# in_root_folder.remove(fileName)

if isSrc:
expected_src_root_folders = ['build-tools', 'changelog', 'dev-docs', 'dev-tools', 'gradle', 'solr']

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dunno why we check for "expected" source root folders at all.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I remember, mainly to assert that nothing new unexpected has crept in. A nice extra explicit assertion on what we intend to ship.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that's an obsolete concern, and we should remove this check altogether. Perhaps long ago the source release was built manually and had risk of including temp/junk but the process today is from what's committed to source control (not the working tree).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants