# Discussion about backporting

**URL:** <https://help.nextcloud.com/t/discussion-about-backporting/233435>\
**Category:** 💻 Development\
**Created:** [October 3, 2025, 11:16am UTC](https://help.nextcloud.com/t/discussion-about-backporting/233435 "2025-10-03T11:16:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![christianlupus](https://help.nextcloud.com/user_avatar/help.nextcloud.com/christianlupus/32/22699_2.png) [@christianlupus](https://help.nextcloud.com/u/christianlupus)\
**Post date:** [October 3, 2025, 11:16am UTC](https://help.nextcloud.com/t/discussion-about-backporting/233435/1 "2025-10-03T11:16:27Z")

</div>

Having seen [2 messages](https://github.com/nextcloud/server/pull/55523#issuecomment-3363502811) about why and how backporting is done in the server, I opened this topic here (to be out of the PR chat).

You know there is typically one branch in the development where the main work is done. This is the `master`, `main`, `trunk`, or whatever called branch. Whenever a new stable release is created, a new branch is created from the current main branch. That way, a series of branches (called `stableX`) are created. For example with the release of NC 32, the branch `stable32` was created.

Generally speaking, one typically only wants to implement things in only one location. That is, typically, one works on the `main` or `master` branch or whatever location represents the current development. Then, when a certain functionality is implemented, one can decide for which versions this is relevant. Then, this is backported appropriately.

We can discuss here further.

Chris

---

<div class="post-metadata">

**Author:** ![SysKeeper](https://help.nextcloud.com/letter_avatar/syskeeper/32/6_22734026db12803ebb3e059622ac3534.png) [@SysKeeper](https://help.nextcloud.com/u/SysKeeper)\
**Post date:** [October 3, 2025, 11:32am UTC](https://help.nextcloud.com/t/discussion-about-backporting/233435/2 "2025-10-03T11:32:13Z")

</div>

Just a side note, we’ve seen an increasing number of seemingly legit questions on github that later turned out to be spam accounts (or preparation for those). Possible that it’s a similar case on the 2 referenced ones. Your original PR also got an approval from a non-member account.

---

<div class="post-metadata">

**Author:** ![christianlupus](https://help.nextcloud.com/user_avatar/help.nextcloud.com/christianlupus/32/22699_2.png) [@christianlupus](https://help.nextcloud.com/u/christianlupus)\
**Post date:** [October 3, 2025, 11:34am UTC](https://help.nextcloud.com/t/discussion-about-backporting/233435/3 "2025-10-03T11:34:30Z")

</div>

I was not sure either and I have seen the unrelated account as well.

However I thought it better to _outsource_ the discussion on the forum and not pollute the PR’s chat

---

<div class="post-metadata">

**Author:** ![SysKeeper](https://help.nextcloud.com/letter_avatar/syskeeper/32/6_22734026db12803ebb3e059622ac3534.png) [@SysKeeper](https://help.nextcloud.com/u/SysKeeper)\
**Post date:** [October 3, 2025, 11:43am UTC](https://help.nextcloud.com/t/discussion-about-backporting/233435/4 "2025-10-03T11:43:15Z")

</div>

> [@christianlupus](#):
>
> However I thought it better to _outsource_ the discussion on the forum and not pollute the PR’s chat

Perfectly valid and I think it is a very good discussion/guideline in general!