Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 2.6.1 #1460

Closed
18 tasks
camilasan opened this issue Sep 30, 2019 · 14 comments
Closed
18 tasks

Release 2.6.1 #1460

camilasan opened this issue Sep 30, 2019 · 14 comments
Assignees
Labels
Milestone

Comments

@camilasan
Copy link
Member

馃敭 The plan

  • RC1: 04.10.2019
  • Final Release: after two weeks time (max) of latest RC release. (27.09.2019)

馃摑 TO DO

/backport to stable-2.6
  • Create tag from branch stable-2.6 created previously
$ git checkout stable-2.6.0
$ git tag -s v2.6.1-rc1 -m "Release..."
$ git push origin --tags
  • 馃彮 Login on the build servers to change the scripts with the current tag and version suffix to build the release:
    • via Parallels for the Mac OS
    • via RDP for Windows
    • via ssh for Linux
  • Move new pkg/exe/AppImage it to download.nextcloud.com/desktop/releases
  • Get changelog using github_helper scripts
  • Create pre-release/release at nextcloud/desktop/releases with the new changelog.
  • 馃敂 Notify Marketing to share the release in the proper channels.

鈿狅笍 TO DO before major releases

  • 馃嵈 Create stable branch (e.g. stable-2.6.0) after tagging RC1 for major release (e.g. v2.6.0-rc1)
  • Update CHANGELOG.md with the new changelog.
  • Bump version in master in VERSION.cmake (e.g. 2.7.0)
@ConstantMown
Copy link

Has issue #124 been fixed in this release?

@TP75
Copy link

TP75 commented Oct 22, 2019

I would like to thank @misch7 for making me aware of the 2.6.1 RC1 desktop client.

By this and by help of the community a nasty groupfolder issue could be solved in a more due time I presume. Furthermore, this was a good opportunity for testing and discussions on NC design aspects in our own little team.

After installation to several client machines in a Nextcloud 16 closed service we collected some issues and made some minor observations. In the outcome of these trials I would like to present a little addendum to the 2.6.1 bucket list for your kind consideration. 馃槆

Hope this helps. Naturally, no obligations and any labels or priotities and milestones are up to deliberations of the developers. 馃槈

Keep on the good work. Happy hacking. 馃憤

@camilasan
Copy link
Member Author

For everyone, you can find the links to download the rc1 here: https://github.com/nextcloud/desktop/releases/tag/v2.6.1-rc1

Thanks for testing @TP75 and opening issues!

@TP75
Copy link

TP75 commented Oct 23, 2019

@camilasan You are welcome.

A new one: #1551

However, related to #1545 apparently.

@ivaradi
Copy link
Contributor

ivaradi commented Oct 28, 2019

It seems that tagging does not trigger a Drone build. I have tested it with my own Drone server installation, and it should work, if enabled in the configuration. Could someone, please, check if this is enabled in the Nextcloud Drone server?

I can produce the stable source packages by running the build manually (as I did for 2.6.0), but it would be nice if the automatic build system could also produice the release packages.

@mjakovina
Copy link

mjakovina commented Oct 30, 2019

@camilasan Does it make sense to mention here that issue #896 is still a problem for significant range of devices (Intel UHD 620 and more)? The client just does not start.

@GoetheG
Copy link

GoetheG commented Nov 3, 2019

What about the end-to-end encryption? Why did this function disappear into thin air after you promoted is in a broad way?

@TP75
Copy link

TP75 commented Nov 8, 2019

Release 2.6.1 and no RC2 ? QM ?
0_0

Thanks for the coding to the devs anyway.
馃憤

@mjakovina
Copy link

Just installed 2.6.1stable-Win64 (build 20191105).
Issue #896 is still a problem (will not run on Intel UHD 620 graphics on Windows)

@GoetheG
Copy link

GoetheG commented Nov 11, 2019

Ihave tow issues with this software version:

  1. No further information on the end-to-end-encryption.
  2. Thereis always one file which cannot besynced.The Nextcloud desktop app cannot upload this one 77 megabyte PST file I have. I always have to rename it before the upload can proceed. This error occurs on every Nextcloud desktop version after 2.5.2.

@TP75
Copy link

TP75 commented Nov 11, 2019

1. No further information on the end-to-end-encryption.

for the E2E there should be an open issue and you should make a search and add to same, if I may

@TP75
Copy link

TP75 commented Nov 11, 2019

2\. Thereis always one file which cannot besynced.The Nextcloud desktop app cannot upload this one 77 megabyte PST file I have. I always have to rename it before the upload can proceed. This error occurs on every Nextcloud desktop version after 2.5.2.

IMHO this would be a server and/or files app issue

However, the NC desktop App can only sync what the NC server accepts

@GoetheG
Copy link

GoetheG commented Nov 12, 2019

@TP75 Thanks for your reply. My server accepts any file. But there seems not to be a pattern. Now it's not syncing another file with less than 100 megabyte. When I uninstalled Nextcloud 2.6.1 and installed Nextcloud 2.5.2 again everything worked fine. Nextcloud Server version is 16.

@TP75
Copy link

TP75 commented Nov 12, 2019

@TP75 Thanks for your reply. My server accepts any file. But there seems not to be a pattern. Now it's not syncing another file with less than 100 megabyte. When I uninstalled Nextcloud 2.6.1 and installed Nextcloud 2.5.2 again everything worked fine. Nextcloud Server version is 16.

@GoetheG May I propose you make a new issue by using 'reference in new issue' to your own comment?

Please consider to download and enable the NC issuetemplate app as this could help in producing the appropriate details for reports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants