foundry revisit (part 2)

README.md

Here are some paper notes from a few days ago. They should be superceded by the "foundry revisit" gist.

• On foundry command, list "`plugins found" and "plugins selected" along side usage
• Add step to verify we are logged in and set up properly (e.g. .git exists, .pypirc has login info, npm is logged in)
• For Python, consider full rebuild? foundry-release-python ... maybe doesn't seem like it will scale well =/
• Move to framework and CLI invoker
  • Universal API for all languages
  • foundry-release-git update-files
  • foundry-release-git publish
• Stop using foundry as a global
  • Always bundle either via bash, npm, or pypi variant
  • git-release -> release in repo
  • I think we were saying to always include release process in our repos. For git only ones, we can prob keep it light with a bash script (no foundry needed)
• Instead of CLI trust, what about required keys in package.json?
  • "release": ["git?", {"npm": {"path": "app/package.json"}}]`
• By twolfson-release, I meant on all in one solutions with if/elses (but a built a plugin repo too)
• foundry make --plugins required or --auto-plugins
• --plugins becuase want to establish trust
• Somehow monitor all fs/exec but impossible to reproduce
• Maybe build twolfson-release but plugins make most sense for case by case (i.e. repo by repo)

---

New thoughts after transcription:

• Upon command running, echo each command we are using (e.g. Running "foundry-release-git update-files")
• Upon failure, list out commands for user to run by hand? Or maybe some form of resume? (e.g. We failed to complete foundry release. We have recorded our progress to foundry-run.log. Once the errors are addressed, please run foundry resume to continue publication)