Release 3.4.2

[allexzander]

📝 TO DO

• ⬆️ Bump VERSION.cmake to 3.4.2 and doc/conf.py (release to 3.4.2) in the corresponding stable branch
• 🏷️ Create tag from corresponding stable branch on the commit introducing the version bump

$ git checkout stable-3.4
$ git pull
$ git tag -s -m "Release 3.4.2" v3.4.2 
$ git push origin --tags

• 🏷️ Create tag from corresponding stable branch in client-building. Steps to create the tag are the same as the above.
• 🏭 Trigger the builds on brander and wait for them to succeed:
  • 🐧 Linux
  • 🍎 Mac OS
  • 🚪 Windows MSI
• 🧪 Execute the bugfix release test plan for each build:
  • 🐧 Linux
  • 🍎 Mac OS
  • 🚪 Windows MSI
• 📖 Get changelog using github_helper scripts, with previous X.Y release as origin point
• 📖 Create draft pre-release at:
  • nextcloud/desktop/releases with the changelog
  • nextcloud-releases/desktop/releases
• 📦 Upload binaries to:
  • the draft pre-release at nextcloud/desktop/releases
  • the draft pre-release at nextcloud-releases/desktop/releases
  • download.nextcloud.com in the user home directory (so still private)
• 🗝️ Sign binaries (ssh -P 2200 to signing VM, then, cat how-to-sign, then scp -P 2200 to download signatures)
• 🛎️ Notify Marketing that the release is ready
• 🚀 When marketing gives the go then publish the draft pre-releases created previously at:
  • nextcloud/desktop/releases
  • nextcloud-releases/desktop/releases
  • run the publish_desktop.sh script on download.nextcloud.com so that the binaries appear at download.nextcloud.com/desktop/releases
• 🆙 Change the updater server config to serve the release
• 🆙 Change the install-clients config to update the link to the latest release on Nextcloud website

[ghost]

3.4.2 seems not to solve #4141 as far as I can Tell. 🙈

[bendschs]

What about #4106?
There seem to be quite some people out there, that are not able to use 3.4.1 at all ...

[ghost]

@allexzander

Wenn I select open issues wit Feature sync engine, I find 69 Items.
Should that not have priority to solve before releasing v3.4.2?

[allexzander]

@allexzander

Wenn I select open issues wit Feature sync engine, I find 69 Items. Should that not have priority to solve before releasing v3.4.2?

@Lars1963
They are indeed of high priority. But, trust me, we have a lot of work every day, and, if something is not fixed quickly, that means we are working on something else that has a higher priority. Also, I am not the one who decides on priorities.

[ghost]

@allexzander
I respect the work you're doing very highly. But,... this problem affects your paying customers equally to the non-paying user of nc. So I can't really understand, that it isn't of higher priority.

The same behaviour existed with the unreliable groupfolder-app, which unfortunally led to no longer using nc as a paying customers for my firm.

[allexzander]

@Lars1963 My knowledge of the business part is limited. I am just a developer.

[smehmetoglu]

I install this version but not working. I found in logs this bu t on my computer i dont have this user. Why is looking for this user.

2022-01-28 11:53:05:130 [ debug nextcloud.sync.database.sql C:\Users\sysadmin\AppData\Local\Temp\2\windows-9041\client-building\desktop\src\common/ownsql.h:145 ] [ OCC::SqlQuery::bindValue ]: SQL bind 2 0

[bendschs]

@allexzander
Wenn I select open issues wit Feature sync engine, I find 69 Items. Should that not have priority to solve before releasing v3.4.2?
@Lars1963
They are indeed of high priority. But, trust me, we have a lot of work every day, and, if something is not fixed quickly, that means we are working on something else that has a higher priority. Also, I am not the one who decides on priorities.

i respect the work you are doing as well very much and i enjoy using nextcloud, still i am wondering if your priorities are set right then, isn‘t syncing the core feature of nextcloud that literally every user needs in order to make use of it? If that one is not working reliably nextcloud would just be worthless for most users i'd guess.

on 3.4.2 the client at least does not freeze any more an macos monterey, but as @Lars1963 me and my users are experiencing a lot of issues with files not being synced for mainly two reasons.

• white space at the end of file (?)
• 404 error

[jospoortvliet]

@bendschs The fact that there are still bugs doesn't mean we stop releasing bug fixes... We can't fix them all at once. And some are more important than others, in particular - if a customer submits an issue in our support system, their bug gets fixed and released as soon as possible.

In the mean time, we can't stop feature development either as we have customers requiring certain features. So yes, it all happens, in parallel, and takes time ⏳

Edit: and to add, obviously we work as fast as we can and you're right that, of course, fixing as many of these important issues is high on our radar. We simply can't fix them all at once so we release minor releases that each fix a few of them at a time - that is all I'm saying!