chore: prepare a new release 1.7.0

[joshtrichards]

Closes #1521
Closes #1558
Closes #1557
Closes #1547
Closes #1543
Closes #1539
Closes #1491
Closes #1489

We've had many fixes and enhancements merged since the last release ~10 months ago (and some of the fixes are required to run on recent NC versions), I think it's about time we get a release out. ;-)

Don't typically work in this repo, so not certain of the release process here. I've tried to reverse engineer it a bit. It appears there is a dedicated release publishing workflow that will be triggered we tag a release and merge into the release branch.

• Bump version in info.xml
• Merge updated info.xml
• Tag v1.7.0 commit
• Generate GH release
  • Generate release notes
• Trigger app store release
  • merge v1.7.0 tag into dedicated release branch

[CarlSchwan]

I can do the actual release tomorrow, I should have the access right now

[flattopc]

I know everyone has day jobs, but I'd be very grateful if this could be reviewed and released! Trying to use Maps for mutual aid in Minneapolis!

[FadeFx]

any chance to get this into 1.7.0?
#1532

[JoaoVictorLouro]

What are we missing here?
How can we help?
I think a lot of people are waiting for this fix, and we are eager to help, but there is close to no transparency :/

[Wrong-Code]

@CarlSchwan and @joshtrichards, thank you both for your efforts. I really hope you can finalize the release and make it public, there are many people (including me) waiting for it to finally upgrade to the latest NC version.

As @JoaoVictorLouro recently commented, is there anything we can help to move on the project?

[TheRaven500]

How's it looking? We're eagerly awaiting the new version. 🤓

[browsingman]

Seems as if the other three members still need to do the review. Would also love to see moving this forward as I depend on the funcitonality of maps as well. And as a featured app I would expect it to work with the latest Nextcloud release. Otherwise it should not be "featured".

So to the other reviewers:
I would really really appreciate if you could take your time to review the release and approve it if possible.

[browsingman]

Other recommendation:
Maybe you could just enable automated generation of nightly builds. That way people would not need to wait eagerly, but could try the nightly build.

Not everybody is able to download the tar archive and compile it with composer / npm / make command by itself.

[TheRaven500]

Other recommendation: Maybe you could just enable automated generation of nightly builds. That way people would not need to wait eagerly, but could try the nightly build.

Not everybody is able to download the tar archive and compile it with composer / npm / make command by itself.

This is a good point. I am able to build maps, but only with the official git repository. I have no clue how to compile and test 1.7.0. 🤷‍♂️

[hayvan96]

Seems as if the other three members still need to do the review. Would also love to see moving this forward as I depend on the funcitonality of maps as well. And as a featured app I would expect it to work with the latest Nextcloud release. Otherwise it should not be "featured".

So to the other reviewers: I would really really appreciate if you could take your time to review the release and approve it if possible.

Or maybe the 3 members could allow @CarlSchwan to release without their explicit approval, especially if they have no time nor motivation to do so.

[Wrong-Code]

So to the other reviewers: I would really really appreciate if you could take your time to review the release and approve it if possible.

At the risk of being downvoted and/or considered unpopular, I would not hold my breath. AFAIK one of those reviewers at least was the original Maps maintainer who switched to another project (GpxPod I think) and we haven't heard from him since. All the bugs and PR of the last 12 months went to deaf hears, and frankly I would not expect to catch their attention now for an approval.

To @CarlSchwan and @joshtrichards: I deeply appreciate the efforts you've put in having prepared in so short time a potential new release with the needed fixes. I am too ignorant in GitHub's project management, so I don't know if this approval process is compulsory or less.

I can only state my case: I am on this cliffhanger since months waiting for a thing which will maybe never get there. Stuck to NC31 (32 with an hack), stuck to Debian 12, etc. Then you came up and stated you could release the new version tomorrow, but another three weeks went through. No further communication since then, so how are we supposed to read that?

I am starting questioning, reluctantly, if I should move away from NC as a whole.

Thanks

Edit: typos

[browsingman]

Ok,
I now took the time to download to install composer, npm and node.js so that I could generate the missing .js files on my local server. Although the generation was showing 37 warnings, the compilation ended successfully.

After replacing my maps directory with the compiled one, my nextcloud instance now is able to use the maps application within NC 34.

Obviously file scanner complains because it did not generate checksums for each file, but I don´t care about that for now.

Therefore everybody that wants to use this:
I can recommend the approach of installing composer, npm and node.js locally, then copy the maps archive within the apps2 directory of NC, execute make to generate the missing files and afterwards enable the maps app with the occ command.

Saved my life for now ;-)