As I understand, the term “Backporting” is used to describe a fix which is applied in a future version which is also ported to a previous version. Wikipedia definition is as follows:
Backporting is the action of taking a certain software modification (patch) and applying it to an older version of the software than it was initially created for. It forms part of the maintenance step in a software development process…
For example:
- A problem is discovered and fixed in V2.0. The same fix is ported and applied to V1.5.
What is the term when this is done in the opposite direction?
- The problem is discovered and fixed in V1.5. The same fix is ported and applied to V2.0.
Would the term “Backporting” still apply? Or is there a term such as “Forwardporting” (which amusingly sounds a lot like “Port Forwarding”)?
1
It’s the same as the opposite of a backslash. Everyone wants to call it a forward slash, but really it’s just a “slash.” The opposite of backporting is simply “porting.”
1
This does not generally happen as you would fix said issue in the V2.0 codebase, and optionally backport it. 🙂 In terms of version control, this is simply called merging.
4
I guess I would use the terms: future-proofing or, alternatively, forward compatibility:
From Wikipedia future-proof:
Future proof: The phrase future proofing describes the exclusive process of trying
to anticipate future developments, so that action can be taken to
minimize possible negative consequences, and to seize opportunities.
And forward-compatibility:
Forward compatibility or upward compatibility (sometimes confused with
extensibility) is a compatibility concept for systems design, as e.g.
backward compatibility. Forward compatibility aims at the ability of a
design to gracefully accept input intended for later versions of
itself.
Or both “future-proofing through forward-compatibility”.
Oh the buzzwordry 🙂
Backporting in the opposite direction is just porting, but there’s no reason to do that in the context you describe.
I think the term “backport” refers only to the action of bringing a feature of a new release of a program to an older of the same program, for the benefits of still using it.
As you don’t develop new feature on old, closed, versions no “reverse” backporting exists (if you are, by definition, the version is not old).
What you’re calling a “forwardport”, fixing a problem both in an old and a new verion, is a mere bugfix or patch.
I came here looking for an answer because I’m writing a commit comment for this very scenario. Given the lack of actual jargon for this common situation, I’m just going to spell it out as “merging production hotfixes into dev branch”.
There is not a commonly used term for merging a set of changes from an older branch of software to a newer one. Unless the latest branch of the software is highly unstable most developers will develop bug fixes on the latest branch of the software regardless of what version the bug was found in. This is done in order to reduce merge conflicts since the latest branch of the software changes more frequently than older branches. Any software bug reported by a customer is by definition reported in an earlier version than it is fixed in since the customer doesn’t have access to the latest branch of your software.
1