| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This updates the bug tracker URL from http://rt.perl.org
to https://rt.perl.org.
There is a place in the code, in corelist.pl, that is sensitive
to the URL of the bug tracker. This now understands both
versions of the bug tracker URL. Ideally, this will be
consolidated once the dust settles.
This patch also updates ExtUtils::CBuilder, Safe, threads
and threads::shared to point to the new bug tracker URL.
|
|
|
|
|
|
| |
This commit moves more URLs from http to https. This time it
affects some source code, that's why it is not bunched up
with the commits affecting pod/*
|
|
|
|
| |
e.g. as done at https://github.com/perlorg/perlweb/pull/289
|
| |
|
|
|
|
| |
..as the updated modules section is generated automatically when perldelta is finalized
|
| |
|
| |
|
| |
|
|
|
|
| |
For: RT 134053
|
| |
|
| |
|
|
|
|
|
| |
Add note concerning the bump of PERL_API_* constants
for blead point releases.
|
|
|
|
| |
It's installed in the same directory (bin) as perl it self.
|
| |
|
|
|
|
|
| |
See <http://nntp.perl.org/group/perl.perl5.porters/252271> for
contextual detail around this removal.
|
|
|
|
| |
shown how to use
|
|
|
|
|
| |
due to re-allocation of available hosts, Tux has now hosted the smoke
reports somewhere else
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Many of the mistakes made by me during a release has to do with the
confusing instructions in the guide.
* Some steps are mentioned in different order
* Some steps are mentioned (and noted to *NOT* do)
* The confusion between "MAINT" and "BLEAD-FINAL", and "BLEAD-FINAL"
and "BLEAD-POINT".
This generator generates a checklist with only the instruction you
*will* have to perform. Any steps that mentions they must be skipped
for the release will not be included in the end-result.
Unlike the previous guide, you need not know the type of the release
you do. Instead, you give the version you want to release and it
generates the appropriate one for you.
All the following incantations work:
perl Porting/make-rmg-checklist --version 5.26.0-RC2 # RC
perl Porting/make-rmg-checklist --version 5.26.0 # BLEAD-FINAL
perl Porting/make-rmg-checklist --version 5.27.0 # BLEAD-POINT
perl Porting/make-rmg-checklist --version 5.27.1 # BLEAD-POINT
perl Porting/make-rmg-checklist --version 5.26.1 # MAINT
Extra benefit: Apparently it includes additional checklist steps
at the top that somehow are not included when you currently generate.
Downside: HTML is not yet supported.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This was noted by Jarkko was a missing instruction for something
that tends to fail but we usually don't notice. ("We" here excludes
Jarkko who randomly finds this broken without us noticing.)
I wasn't sure where to put this, but preparing the tarball seems
like an appropriate time.
|
|
|
|
| |
Incorporate feedback from Aaron Crane.
|
| |
|
|
|
|
|
| |
I found these three similar filenames hard to read when flowed into a single
paragraph.
|
|
|
|
|
| |
New perl releases are detected via an every-hour cron job, which will
update the relevant custom fields. This step is thus now unnecessary.
|
|
|
|
| |
A literal / (solidus) is E<sol>.
|
| |
|
| |
|
|
|
|
|
| |
These were discovered while testing the Pod::Checker that is intended to
be used in 5.25.
|
|
|
|
|
|
|
| |
Each time I do a release, I find myself scrambling to download the
tarball of the previous release, and install it so it can be compared
to the release that's worked on. Added a paragraph as a reminder to
that before the day of the release.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This trips me each and every time I make a release. Whenever the
release manager guide calls for a compile/make test cycle, I run
"make test_harness", and this fails at this stage, because Module::CoreList
has not been updated yet (the next action described in the release
managers guide is updating Module::CoreList).
I also removed some suboptimal advice I've written here in the past.
|
|
|
|
| |
So we can easily copy-and-paste it.
|
|
|
|
| |
So, I removed the references that it wasn't working in December 2015.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
I checked with Graham Barr, who said the list of PAUSE accounts
that can upload perl distributions is automated and taken from:
http://pause.perl.org/pause/query?ACTION=who_pumpkin;OF=YAML
This means that if you're already on the list, you do not need
to check again on search.cpan.org or to bug Graham. :)
|
| |
|
| |
|
|
|
|
| |
This fixes a bunch of them, but there are many more
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|