ToDo

[boennemann]

Instead of opening issues in this repo one by one I'll first dump my brain into this issue so I can get my thoughts in order and don't forget stuff while being busy pressing a lot of buttons.

In no particular order:

Code

• De-babelify the source, to remove barrier to entry, remove buildstep overhead, better tooling integration (e.g. coveralls) (At some later point deprecate node <4 and use natively avail. es6)
• republish all core components as unscoped packages (or fix bundleDependencies and scoped packages don't work together npm/npm#9175) so semantic-release can have bundled, deduped and flattened dependencies (single tarball, such speed, wow) https://github.com/boennemann/dynamic-bundle
• find better names for plugins, more like event names "verification", "condition", "releasenotes", "lastrelease"
• implement all those plugins at the top of the readme
• proper website
• update commit-analyzer to latest version of conventional changelog and potentially support other styles (way more work involved than it sounds 😬)
• accept both BREAKING CHANGE: and BREAKING CHANGES: i.e. be looser here because ignoring a breaking change declaration has some dangerous consequences
• get integration tests running, use npm-registry-mock
• make github independent, move that into core plugins, get gitlab going
• fix travis-after-all for private/enterprise https://github.com/alrra/travis-after-all
• fix CLI on windows
• remove obscure keychain defaults Keychain usage / documentation cli#25
• implement plugin pipeline for release-notes as well, where one can modify the previous result
• by default add release notes plugin that extracts all commiters and thanks/mentions them in the notes
• by default add condition plugin that checks for insecure files https://github.com/bahmutov/ban-sensitive-files
• find a way to verify commit messages, so the publish fails if not all commits are according to the conventions
• tests for the cli

Community

• reboot semantic-release as an OPEN open source project
• spread the work on more shoulders
• find core team responsible for project and future direction, no more "@boennemann top-down"
• reply to and review issues/prs in a timely manner
• be present and have questions answered in gitter chat room
• call for contributors, invite core team, be generous with commit bits
• when these bulletpoints get rewritten as individual issues make them myfirstpr compatible

Documentation

• be better at describing what semantic-release is and how it works
• be better at describing all the pro/power features: e.g. release channels
• be better at describing how flexible semantic-release is, both with plugins and external scripts/wrappers

to be continued/refined