Ignorance reduction: Evaluate current state of affairs

[edburns]

• Look at publish.yml. Is it just a big long workflow with jobs for each language in sequence?
  • Is that how we want to continue to do it?
  • Benefits of doing it this way?
  • Negatives of doing it this way?
• Explore alternatives
  • Keep publish.yml but have it call out to net-new workflows for the languages. Essentially, decompose the per-language code into language-specific workflows.
  • Keep publish.yml exactly as is, but have it call out to java-publish-maven.yml at the end.

[github-actions]

This issue couldn't be automatically classified into one of the standard categories (bug, enhancement, question, or documentation).

The issue appears to be a meta/infrastructure investigation task — it asks for an evaluation of the current publish.yml CI/CD workflow structure and exploration of architectural alternatives (decomposing per-language publish steps into separate workflow files). This is closer to a process/infrastructure discussion than any of the standard issue types.

A human reviewer will need to triage and assign the appropriate label.

Generated by Issue Classification Agent for issue #1872 · sonnet46 282.6K · ◷