Idea Summary
My idea is to centralise the p_release parameter in set_environment.sql file for split APEX export files instead of repeating it in each file (like pages, shared components, etc.). 

Use Case
As part of the development workflow, I work with a GIT repository to track changes in the APEX application and I try to review exported app before commiting it. When a new patchset is applied and the application is re-exported, every file that contains the p_release parameter appears as modified, even though the actual application logic may not have changed. Things get more complicated if you happen to be working on changes on multiple pages and a patchset is installed. In that case, you have to review all files to make sure there are only your changes that will be commited.

By centralising the p_release value in just one file, we can reduce unnecessary diffs and improve clarity in the repository.

Preferred Solution (Optional)
Make the p_release parameter required only for wwv_flow_imp.import_begin procedure. Others procedures (like wwv_flow_imp.component_begin) should use the release value provided for wwv_flow_imp.import_begin procedure. The line with p_release parameter should be removed from all files except set_environment.sql