How to Get Your Release Through the Incubator
summary
Explains exactly what reviewers check: source releases must not contain binaries, must use correct ASF headers, signed artifacts with tag hashes, and clear LICENSE + NOTICE assembled to reflect bundled files; common failures and fixes are shown with tools like RAT and simple grep scripts plus a web checker; licensing is split into category A/B/X (GPL is X) and nuanced examples (Bootstrap glyphicons, minified JS, fonts, even a copyrighted cat photo) and operational stats (about 200 reviews seen, ~70% pass, ~12 releases/month).
AI-written summary · about
chapters (34)
- 0:00Intro
- 0:41I am not a Lawyer
- 1:50Incubating Projects
- 3:46Incubator Vote Process
- 6:10State of Play
- 7:59Required Reading (cont)
- 9:11Why I voted - 1
- 15:30Make it Easy to Review
- 16:06Not One Right Answer
- 17:27Top Level Projects
- 18:53Disclaimer
- 20:48Developers vs Licensing
- 23:52Documentation Issues vs Errors
- 24:28Universal Donor
- 25:07Guiding Principle
- 28:57Compliance Rocks!
- 29:23Finding Licenses
- 30:59Other People's Cat Photos
- 31:53Troublesome Fonts
- 32:36Legal vs Policy
- 33:11License File
- 34:40Notice File
- 36:05Required Notices
- 39:30No Unexpected Binary Files
- 40:19Headers
- 41:15Can Compile
- 41:48Apache Wombat
- 42:22Wombat Walk Through
- 44:33Nice to Haves
- 45:10Common Mistakes
- 45:59Binary Distributions
- 47:05The incubator is broken
- 50:26Other Tools
- 50:54Questions?
related talks
46mHow to Slide Your Release Pass the Incubator
29mNavigating Podling Releases: Achieving Success in the Apache Incubator
41mHatching The Clutch - A Guide to the Apache Incubator
28mReleasing binaries in the Incubator
50mRunning a Successful Open Source Project
36mGuidelines for Achieving Project Release Maturity
39mA decade of lessons in Open Source licensing
14mOpen-source it right (and avoid calling your IP lawyer)!