On Mon, Mar 20, 2023 at 3:55â¯PM demerphq <demerphq@gmail.com> wrote: > There is an awful lot of manual stuff in that process that IMO could be > automated, and at least some that I wonder if it really is necessary > (comparing the files from one release to another for instance, isnt that > what the MANIFEST is for?). Definitely a todo list where experience would > make a difference in how long it takes. > I don't do that. I also skip most of the places in the RMG that have you doing a git -dxf; ./Configure ...; make test and save that for the end. 80% of the time I spend is reviewing every commit (on average there are about 200 of them between releases) for sanity and the possible need for a perldelta, 10% of the time is spent editing the perldelta file itself, and the rest is jumping around in the RMG looking for references to Module-CoreList because the positioning is all wrong for blead releases, for a total of about 4-6 hours (much of which can be done in advance of the day).Thread Previous | Thread Next