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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add v2023.2 release notes #3068

Merged
merged 1 commit into from
Jan 5, 2024

Conversation

skorpy2009
Copy link
Member

No description provided.

@github-actions github-actions bot added the 3. topic: docs Topic: Documentation label Nov 24, 2023
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
@T-X
Copy link
Contributor

T-X commented Dec 3, 2023

Maybe add a section to name the new OpenWrt, Linux kernel mac80211-backports like we had for v2022.1? Also the (potentially, if most nodes were updated) new handling of IPv6 multicast packets with a routable address, enabled due to the newer Linux kernel/bridge version, migh be worth mentioning. Suggestion:

Major changes
-------------

OpenWrt
~~~~~~~

This release is based on the newest OpenWrt 23.05 release branch. It ships with Linux kernel 5.15, wireless-backports 6.1.24 and batman-adv 2023.1. 

...

Minor changes
-------------

batman-adv
~~~~~~~~~~

If enough nodes are updated then the batman-adv multicast optimizations originally introduced in Gluon 2021.1 for link-local IPv6 multicast addresses will then be applied within the domain to routable IPv6 multicast addresses, too.

@blocktrron
Copy link
Member

Updated to contain all changes introduced up to 32256ef

@herbetom
Copy link
Contributor

herbetom commented Dec 22, 2023

Linking PRs to changes would have been a nice touch.

Might not work everywhere but at least for some parts. I think it can help demystifying stuff and helps quickly understanding changes/context when the Release Notes might be unintentionally lacking some Infos.

docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
@skorpy2009 skorpy2009 force-pushed the skorpy/v2023.2 branch 2 times, most recently from eba366d to 5eff4a1 Compare December 26, 2023 12:58
@rotanid rotanid added this to the v2023.2 milestone Dec 26, 2023
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
@skorpy2009 skorpy2009 requested a review from neocturne December 28, 2023 23:03
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
docs/releases/v2023.2.rst Outdated Show resolved Hide resolved
@blocktrron
Copy link
Member

@neocturne I can not comment on your remark about the removed device support. I've updated this section accordingly.

@herbetom
Copy link
Contributor

@blocktrron I can't see any upated commits?

@skorpy2009
Copy link
Member Author

@neocturne yes please just push in here :)

@neocturne
Copy link
Member

I have pushed 3 commits with suggested changes.

Copy link
Contributor

@herbetom herbetom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2023 is over. I would propose renaming this release to v2024.1.

@skorpy2009
Copy link
Member Author

2023 is over. I would propose renaming this release to v2024.1.

No

@blocktrron
Copy link
Member

In case anyone wants to refactor everything, go ahead. I'll not be the one bikeshedding this further.

@neocturne
Copy link
Member

I can take care of the renaming if we want to switch to 2024.1.

@2tata
Copy link
Contributor

2tata commented Jan 1, 2024

I can take care of the renaming if we want to switch to 2024.1.

I can help as well.

Signed-off-by: Magnus Frühling <[email protected]>
@blocktrron blocktrron merged commit 4aba392 into freifunk-gluon:master Jan 5, 2024
10 checks passed
hafu pushed a commit to Freifunk-Potsdam/gluon that referenced this pull request Jun 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. topic: docs Topic: Documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.