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

v8.8.0 #5328

Merged
merged 2 commits into from Feb 29, 2024
Merged

v8.8.0 #5328

merged 2 commits into from Feb 29, 2024

Conversation

ShGKme
Copy link
Contributor

@ShGKme ShGKme commented Feb 29, 2024

v8.8.0 (2024-02-29)

Full Changelog

What's Changed

馃殌 Enhancements

馃悰 Fixed bugs

Other Changes

Antreesy and others added 2 commits February 29, 2024 11:22
Signed-off-by: Maksim Sukharev <antreesy.web@gmail.com>
Signed-off-by: Grigorii K. Shartsev <me@shgk.me>
@ShGKme ShGKme added the 4. to release Ready to be released and/or waiting for tests to finish label Feb 29, 2024
@ShGKme ShGKme added this to the 8.8.0 milestone Feb 29, 2024
@ShGKme
Copy link
Contributor Author

ShGKme commented Feb 29, 2024

For version 8.8.0 the hash started with 8e452 with was used as a number.

8E452 = 8 * 10 ^ 452 = infinity.

So full hash 8e452f0 was compiled as calc(infinity * 1f0)

@Antreesy Antreesy merged commit 791207d into master Feb 29, 2024
19 checks passed
@Antreesy Antreesy deleted the v8.8.0 branch February 29, 2024 12:20
@susnux
Copy link
Contributor

susnux commented Feb 29, 2024

Can we please have somekind of schedule for releases? Or at least some more time to prepare?
It is a bit annoying if you have library changes required for app / core that blocking you, you will have to either spam another minor release or wait another week or so what is critical in the current release schedule of a server beta every 3 days.

@nickvergessen
Copy link
Contributor

Sounds good to me. We just did a release as we want to release Talk and there were unacceptable issues with the existing release

@ShGKme
Copy link
Contributor Author

ShGKme commented Feb 29, 2024

@susnux I'm not sure, I understand what you are bothering about...

If it is about a possibility to break a release, then we probably should have beta @nextcloud/vue releases for minor updates. So we can check it on beta and rc releases for server and apps before making a stable library release.

If it is about adding changes to the release required by server/app, then it should not be a problem. We always can make a new release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4. to release Ready to be released and/or waiting for tests to finish
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants