On Oct 2, 2015, at 12:38 AM, Andrew Bayer <[email protected]> wrote:
> So - what exactly should Yetus's build system look like? What are our > deliverables? What do we need to run during the build? Awesome! Thanks for working on this! I’ll let Sean cover the annotations bit, but IMHO on the rest of it… I think the deliverable should be one tar ball. It should support the follow dirs/content: * Standalone executable chunks, in either a single bin dir or multiple by ‘project': - releasedocmaker.py - shelldocs.py - everything else in dev-support, which I tend to refer to as ‘precommit’ * Documentation in a docs dir: - Contents of asf-site-src/source/documentation/latest - shelldocs.py should be run against test-patch.sh to generate an API document for test-patch plugins (this is also something that should get added to the website. argh forgot!) - releasedocmaker.py output (we have some work here for yetus tho — fix release notes in jira, make important as a separate section) Build system should also support: * Unit Tests - At some point, I’ve got some unit test code for some of test-patch’s API that we’ll definitely want run. - need to add unit tests for the python bits * RAT (of course) * I think it would be *nice* but clearly optional if we could generate the publish directory of the website as part of the build system. I’m sure I’m missing things, but this is probably a good starter list. > During the Lightning Talks, Shane Curcuru did his regular attempt to recite > all the ASF projects in reverse alphabetical order in ~2 minutes - he > didn't succeed, in part because he took time before starting to celebrate > the fact that the ASF now has a Y. =) That’s awesome! :D Sean and I rushed to get yetus.apache.org up just in case it came up. :D
