Releasable
Pages 28
General Info
Home
Channels
Installation
Benchable
Bisectable
Bloatable
Committable
Coverable
Evalable
Greppable
Linkable
Nativecallable
Notable
Quotable
Releasable
Reportable
Shareable
Sourceable
Squashable
Statisfiable
Tellable
Undersightable
Unicodable
For Maintainers
Installation (for maintainers)
Testing
Adding New Features
Clone this wiki locally
This is an IRC bot for getting information about the upcoming release. It can be addressed by its full name ('releasable6') or its short name ('release').
As a user, you are probably only interested in its only command “status”. It tells when the next release is going to happen and how many blockers are there.
If you are a release manager, there are a few other tricks to learn. At this point, the best way to start is to read this commit message. Basically, the bot generates a list of commits that are not listed in the changelog. To “review” a commit, simply add it to the changelog in rakudo repo. If some commit should not be logged, write something like this in your commit message:
Log all changes to date
Deliberately not logged: beefbeef deaddead … …
If you don't want to commit the changelog yet, just upload it somewhere and give it to the bot (releaseble6: changelog https://….…/…/…
). There's no way to ignore some commits this way, but it should be good enough for what you are doing.
Note that the bot accepts various commands (status
, changelog
, when
, next
, …), but they perform exactly the same.
You can find some extra examples in tests: releasable.t
Usage examples
<AlexDaniel> releasable6:
status
<releasable6> AlexDaniel, Next release in 4 days and ≈22 hours. 3 blockers. Changelog for this release was not started yet
<releasable6> AlexDaniel, Details: https://gist.github.com/03d0c3bbcd3b966773b2432056b27da3