Page MenuHomeFreeBSD

www/typo3-8: Update from 8.7.3 to 8.7.4
ClosedPublic

Authored by joneum on Aug 10 2017, 12:45 PM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 20 2024, 7:55 AM
Unknown Object (File)
Dec 22 2023, 11:09 PM
Unknown Object (File)
Oct 25 2023, 5:01 AM
Unknown Object (File)
Sep 8 2023, 1:58 AM
Unknown Object (File)
Aug 10 2023, 12:30 PM
Unknown Object (File)
Aug 10 2023, 12:29 PM
Unknown Object (File)
Aug 10 2023, 12:29 PM
Unknown Object (File)
Aug 7 2023, 10:09 AM
Subscribers

Details

Summary

PR: 221389
Submitted by: Helmut Ritter <freebsd-ports@charlieroot.de> (maintainer)
Approved by: xxx (mentor)
#Differential Revision: https://reviews.freebsd.org/Dxxxxx

Test Plan

~/dev/ports/www/typo3-8 % portlint -AC
WARN: Makefile: for new port, make $FreeBSD$ tag in comment section empty, to make SVN happy.
0 fatal errors and 1 warning found.

poudriere testport:

10.3-amd64
10.3-i386
11.1-amd64
11.1-i386
12.0-CURRENT r321899 amd64
12.0-CURRENT r321913 i386

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Approved with following changes:

This revision is now accepted and ready to land.Aug 10 2017, 12:54 PM
In D11954#248051, @tz wrote:

Approved with following changes:

Can you give me a hint - why MFH? I only see into the Changelog, that this update have bug fixes only.

In D11954#248051, @tz wrote:

Approved with following changes:

Can you give me a hint - why MFH? I only see into the Changelog, that this update have bug fixes only.

Because of the bug fixes. Its a little subjective since the main purpose of the quarterly branch is to be as stable as possible. But letting user stick which unresolved bugs is not better either.

Also there is a Wiki page:
https://wiki.freebsd.org/Quarterly_Branch

There its stated:

t receives only the following Merge From Head (MFH) commits, including, but not limited to:

    [..]
    - Build, run, packaging, or **bug fixes**

Whenever there is no security issue resolved i go through the changelog of the update and ask myself: is just one of the entry worse a MFH? Is there any use which will complain not having this fix? If yes, i request MFH. If not, not. Also if not: remember this next time, when you need a MFH.

Thanks for the explanation. She is very helpful.

This revision was automatically updated to reflect the committed changes.