Release 3.8.1

[mgallien]

📝 TO DO

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

$ git checkout stable-3.8
$ git pull
$ git tag -s -m "Release 3.8.1" v3.8.1 
$ 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
    • ⚠️ Have a look at the build log on brander to also download the delta update file (.tbz) required for automated upgrade: Sharing succeeded (it needs to be signed similarly to .pkg file and uploaded everywhere)
  • 🚪 Windows MSI
• 🗝️ Sign binaries (ssh -P 2200 to signing VM, then, cat how-to-sign, then scp -P 2200 to download signatures)
• 📖 Create draft pre-release and release notes (click on Generate release notes) at:
  • nextcloud/desktop/releases
  • nextcloud-releases/desktop/releases (copy the changelog from nextcloud/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)
• 🛎️ Notify Marketing that the release is ready
• 🚀 When marketing has been notified 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
  • ask sysadmin to update the .htaccess such that latest alias point toward the new release (for example https://download.nextcloud.com/desktop/releases/Windows/latest)
• 🆙 Change the values of $stableReleaseDate and $stableVersion in the updater server config to serve the release.
  • For the mac update service, you need find the value of sparkle:edSignature and length in the brander build log (near the very end of the build log) and replace the values "signature" and "length" under 'macos' in 'stable'.
• 🆙 Change the install-clients page to update the link to the latest release on Nextcloud website (direct modification via wordpress web ui)
• 📧 E-mail the company internal mailing list about the new client: just a reminder for them to update to the latest client and to report any issues they might find.

[bcutter]

When can we expect this? My whole NC is basically blocked because of #5564 for days now, even with only older versions (< 3.8.0), probably as 3.8.1 modified some meta data on the server in a manner which renders sync forever useless. Or it is server app version 1.11.3 now... anyway, E2EE is dead now, thanks.

There's not even a nightly or beta or hotfix or something, right? Gosh...

[eibex]

Is there an ETA by any chance? I haven't been able to use the desktop program for over 2 weeks now since the E2EE errors block any sync activity.

[bcutter]

Is there an ETA by any chance? I haven't been able to use the desktop program for over 2 weeks now since the E2EE errors block any sync activity.

You could remove E2EE (disable on every desktop client which updated to 3.8.0 already) to use the rest of NC without it.

They market 3.8.0 and E2EE and render installations broken for weeks. Would be funny if it wouldn't hurt that much.

[russtaylor]

I don't know about your situations, but I know that I'm using this, without paying a cent, because it's an awesome tool that volunteers have built and maintain. I have no room to demand or be mad about anything. I also know that maintaining open source software can be incredibly demanding and thankless work.

So, @mgallien, thank you for the work you put into this (and to everyone else who contributes to it).

I'm looking forward to this release's bugfix for e2ee whenever it becomes available.

[eibex]

I don't know about your situations

I have no expectations either, and have said thanks on multiple occasions. I just asked if there was an ETA :)

[mgallien]

@russtaylor @eibex
thanks for your support
to everybody, sorry for the very long delay
v3.8.1 should be much more reliable for end-to-end encryption
we also keep working on the reliability of this feature and you may got more fixes soon