---
# System prepended metadata

title: Perl Release To-Do List

---

# Perl Release To-Do List

## Improve the manual release process

### Stuff we can do quickly

* `podcheck` has too many false positives
* Find an alternative commits for Link f7cf42bb69 (not a 5.X.0, one for MAINT and one for BLEAD_POINT, maybe others)

### Stuff that will take several sessions

* prototype `release.sh`
  * don't do the cpan upload step, but okay to hack almost everything else
  * be very careful about not push to upstream blead
* ~~More 5.X.Y (find, bump version etc...)~~ (remaining examples are not straight-forward to fix)
* Templating of the RMG
* Cleanup `Porting/` (i.e. look at every file, decide if it's still relevantm, document it if needed, etc.)

### Scope unclear

* release announcement: automate numbers which specify how many lines/modules are changes in dual-life/cpan (shows that CPAN is also alive and well)
* Break Jump Update Module::CoreList?

### WIP
* Don't try to sync `dist/` stuff (in `Porting/sync-with-cpan`) reported by `Porting/core-cpan-diff` (tib)

## Automate the Perl Release process

How close to a single command can we make the Release Process?

### Stuff we can do quickly

* move all the stuff related to the release process to the `Porting/Release` subdirectory

### Stuff that will take several sessions

* move prereqs (`sync-with-cpan`, etc.) out of the RMG (but properly document them)

### Scope unclear

* include Corion's [rmg-progress-dashboard](https://github.com/Corion/App-rmg-tools) in core?
  * split the above in libraries?
  * add actions, with prereqs
  * prereqs can use the tests from the dashboard
  * map RMG steps to checklist items in the dashboard
* Tib's branch to finalize perldelta

## Done

### Done: Improve the manual release process

* RMG: remove "or perhaps perl5.X.Y" conditionals
* perldelta: [Merge the development deltas into a single perldelta](https://github.com/Perl/perl5/pull/23842)
* Link f7cf42bb69
* No more floating version in perlweb + remove step in RMG (maybe find a new owner, or automate away)
* change the title of the document from "TEB TODO:" to something nicer
* create a HackMD team with the three of us, and attach this document to the team if possible

### Done: Automate the Perl Release process