Doc: Add 3.3 release notes - #1509
Open
roosterfish wants to merge 3 commits into
Open
Conversation
There was a problem hiding this comment.
Pull request overview
Adds the MicroCloud 3.3 release notes to the documentation set and links them from the release notes index so they appear in the published docs.
Changes:
- Introduces a new “MicroCloud 3.3 release notes” page with highlights, bug fixes, and upgrade guidance.
- Adds a new toctree entry so the 3.3 release notes are discoverable from the release notes index.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| doc/reference/release-notes/release-notes-3.3md | Adds the new 3.3 release notes content (highlights, bug fixes, upgrade notes, changelog link). |
| doc/reference/release-notes/index.md | Adds a toctree entry for the new 3.3 release notes page. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
roosterfish
force-pushed
the
release_notes_3.3
branch
2 times, most recently
from
August 19, 2026 10:22
f015536 to
d1e509e
Compare
roosterfish
marked this pull request as ready for review
August 19, 2026 11:26
simondeziel
previously approved these changes
Aug 19, 2026
elijahgreenstein
left a comment
elijahgreenstein
left a comment
Contributor
There was a problem hiding this comment.
A few comments.
Also, generally, the use of "got" for passive voice stands out to me as a bit too casual/informal for documentation. Using "was" or "were" would probably be preferred.
|
|
||
| ### New home for docs | ||
|
|
||
| The integrated doc set got moved to [canonical.com/microcloud/docs](https://canonical.com/microcloud/docs/). |
Contributor
There was a problem hiding this comment.
A small nit ("got" seems fairly casual to me):
Suggested change
| The integrated doc set got moved to [canonical.com/microcloud/docs](https://canonical.com/microcloud/docs/). | |
| The integrated doc set was moved to [canonical.com/microcloud/docs](https://canonical.com/microcloud/docs/). |
Contributor
Author
There was a problem hiding this comment.
Thanks! Fixed now.
| The integrated doc set got moved to [canonical.com/microcloud/docs](https://canonical.com/microcloud/docs/). | ||
| It is now located alongside MicroCloud's [product page](https://canonical.com/microcloud). | ||
|
|
||
| The changes got split across several PRs, see: |
Contributor
There was a problem hiding this comment.
Suggested change
| The changes got split across several PRs, see: | |
| The changes were split across several PRs, see: |
| This allows MicroCloud to omit setting the `network.ovn.northbound_connection` configuration option in LXD. | ||
| LXD can now react immediately on address changes made in MicroOVN. | ||
|
|
||
| Before MicroCloud was updating the `network.ovn.northbound_connection` configuration option only during cluster initialization and |
Contributor
There was a problem hiding this comment.
Suggested change
| Before MicroCloud was updating the `network.ovn.northbound_connection` configuration option only during cluster initialization and | |
| Previously, MicroCloud only updated the `network.ovn.northbound_connection` configuration option during cluster initialization and |
|
|
||
| When deploying MicroCloud clusters using preseed, optional storage filters can be provided to find specific disks to be used | ||
| for local and remote (Ceph) storage. | ||
| The respective how-to guides got extended to show practical usage examples. |
Contributor
There was a problem hiding this comment.
Suggested change
| The respective how-to guides got extended to show practical usage examples. | |
| The respective how-to guides were extended to show practical usage examples. |
Comment on lines
+95
to
+96
| In preseed mode, all of the disks selected for remote storage got checked for existence on the initiator. | ||
| This does not work for disks which got selected on cluster members other than the initiator. |
Contributor
There was a problem hiding this comment.
Suggested change
| In preseed mode, all of the disks selected for remote storage got checked for existence on the initiator. | |
| This does not work for disks which got selected on cluster members other than the initiator. | |
| In preseed mode, all of the disks selected for remote storage were checked for existence on the initiator. | |
| This does not work for disks which were selected on cluster members other than the initiator. |
|
|
||
| The cluster manager is now capable of triggering a defined set of actions through a secure reverse tunnel opened up by MicroCloud. | ||
| For each MicroCloud cluster you can enable the tunnel to be opened up with the already configured cluster manager. | ||
| By default the tunnel is deactivated: |
Contributor
There was a problem hiding this comment.
The command that follows activates it, right? How about:
Suggested change
| By default the tunnel is deactivated: | |
| By default the tunnel is deactivated. You can enable it with: |
Contributor
There was a problem hiding this comment.
Or:
Suggested change
| By default the tunnel is deactivated: | |
| By default the tunnel is deactivated. You can activate it with: |
Contributor
Author
There was a problem hiding this comment.
I have applied the latter. Fixed.
Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
roosterfish
force-pushed
the
release_notes_3.3
branch
from
August 20, 2026 07:25
d1e509e to
ebf80c6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds the 3.3 release notes.