RMG: Simplify the corelist section #23401
Conversation
|
I can't really comment. The wording I added to the RMG 12 years ago just reflected that at the time, handling Module::CoreList was complex as it lived in all branches and needed to be consistently version-bumped. I can't remember the details, and I have no idea what (if anything) has changed or improved in the meantime. |
|
|
||
| The procedure for MAINT releases is not straighforward and implies to pick past | ||
| updates (e.g. from BLEAD-POINT) into the corelist. See | ||
| L<Handling Module::CoreList in MAINT branches (Dave Mitchell)|https://www.nntp.perl.org/group/perl.perl5.porters/2013/03/msg200007.html>. |
There was a problem hiding this comment.
Highlights from the linked message:
I think its happened this way (i.e. people haven't followed the "official"
instructions) because the instructions are impossible to actually follow
in practice.
But I don't really know what's best.
I‡ don't think a procedural checklist for doing a release is the correct time/place for philosophical debate, especially when the debate is about how difficult it is to follow the documented procedure(s)
__
‡. somebody with a github account who's never done a perl release
| $ ./perl -Ilib Porting/corelist.pl ~/my-cpan-mirror | ||
|
|
||
| Otherwise, run: | ||
| In most cases, run: |
There was a problem hiding this comment.
I don't like this wording very much.
To me the "in most cases" is meaningless because when reading that I will start wondering if my current case is part of the "most cases" or if it's one of the exception cases..
(From just the diff it's not clear if/when "most cases" apply, maybe it's from the rest of the context but I didn't read that yet)
|
@bingos would you like to comment on this pull request re |
I am unhappy with the "Update Module::CoreList" sections.
Changes