No subject

avoid unnecessary diverging of the 6.2 code already in early times of =
its support phase.

A consideration which I would like to add is to do an estimation of the =
likeliness whether such a change is breaking for a user and an =
estimation of the effort needed to fix is in case a user is affected. =
Moreover lets add this information as a note to the forge ticket.

For the first patch mentioned, I'd say this likeliness is really low and =
the fix is really easy by simply specifying the parameter for the =
include.

Thanks, Cheers
Markus

> -----Original Message-----
> From: typo3-team-core-bounces at lists.typo3.org [mailto:typo3-team-core-
> bounces at lists.typo3.org] On Behalf Of Helmut Hummel
> Sent: Sunday, July 20, 2014 6:47 PM
> To: typo3-team-core at lists.typo3.org
> Subject: [TYPO3-core] "breaking" changes in minor releases?
>=20
> Hi!
>=20
> How should we handle changes in minor releases, that fix bugs, but =
might
> also break third party code?
>=20
> Here are two examples:
>=20
> https://review.typo3.org/31694
> This would break for users, that rely on the fact that all files from =
a specified
> directory are inlcuded, not only txt and ts files.
>=20
> https://review.typo3.org/20026
> This might break hooks/ XCLASSes, as a public property is removed
>=20
>=20
> In the past we also had security fixes, which broke sites (sometimes =
heavily).
>=20
>=20
> My proposal would be:
>=20
> Allow breaking changes for private API (second example) or "edge
> usecases" (third example; whou would expect .doc files to be included =
as
> TS?) or security fixes, but mark every such change as breaking ([!!!])
> in the commit message, no matter how small such breakage would be.
>=20
> By doing so, we could mor easily inform users about such changes and
> they can decide whether they might be affected or not before an =
update.
>=20
>=20
> What would you do?
>=20
> Kind regards,
> Helmut
>=20
> --
> Helmut Hummel
> Release Manager TYPO3 6.0
> TYPO3 Core Developer, TYPO3 Security Team Member
>=20
> TYPO3 .... inspiring people to share!
> Get involved: typo3.org
> _______________________________________________
> Before posting to this list, please have a look to the posting rules
> on the following websites:
>=20
> http://typo3.org/teams/core/core-mailinglist-rules/
> http://typo3.org/development/bug-fixing/diff-and-patch/
> _______________________________________________
> TYPO3-team-core mailing list
> TYPO3-team-core at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core