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

Release 1.32.0 doc changes #102

Merged
merged 67 commits into from
Feb 27, 2024
Merged

Release 1.32.0 doc changes #102

merged 67 commits into from
Feb 27, 2024

Conversation

JTorreG
Copy link
Collaborator

@JTorreG JTorreG commented Feb 22, 2024

Release 1.32.0 branch

Adds all the documentation changes related to Unit Release 1.32.0

Planned changes:

  • Version change
  • Date change
  • 1.32.0 Release news doc
  • wasm-wasi-component news doc
  • wasm-wasi-component doc changes
  • ...

This PR is a work in progress. The planned changes above will be updated as we go.

@JTorreG JTorreG self-assigned this Feb 22, 2024
Copy link

netlify bot commented Feb 22, 2024

Deploy Preview for nginx-unit ready!

Name Link
🔨 Latest commit ce6127a
🔍 Latest deploy log https://app.netlify.com/sites/nginx-unit/deploys/65ddee87a064b3000811830b
😎 Deploy Preview https://deploy-preview-102--nginx-unit.netlify.app/howto/falcon
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@ac000
Copy link
Member

ac000 commented Feb 22, 2024

Release 1.32.0 branch

Adds all the documentation changes related to Unit Release 1.32.0

...
* 1.32.0 Release news doc
* wasm-wasi-component news doc
* wasm-wasi-component doc changes

Is there some missing commits? or is that the more to come?

@tippexs
Copy link

tippexs commented Feb 22, 2024

.

There is more to come. We are currently working on the commits.

@ac000
Copy link
Member

ac000 commented Feb 22, 2024

A couple of issues I see here

  1. Line lengths

I think we should stick to keeping our lines < 80 characters wide where possible, obviously commands, URL's etc should not be wrapped.

  1. White space damage

These patches introduce a fair amount of excess whitespace

$ git diff --check master.. | grep -v ^+ # because the highlighted whitespace won't show here
source/configuration.rst:5137: trailing whitespace.
source/configuration.rst:5140: trailing whitespace.
source/configuration.rst:5141: trailing whitespace.
source/configuration.rst:5149: trailing whitespace.
source/configuration.rst:5150: trailing whitespace.
source/configuration.rst:5152: trailing whitespace.
source/configuration.rst:5153: trailing whitespace.
source/configuration.rst:5154: trailing whitespace.
source/configuration.rst:5163: trailing whitespace.
source/configuration.rst:5167: trailing whitespace.
source/configuration.rst:5168: trailing whitespace.
source/configuration.rst:5169: trailing whitespace.
source/configuration.rst:5171: trailing whitespace.
source/configuration.rst:5172: trailing whitespace.
source/configuration.rst:5177: trailing whitespace.
source/configuration.rst:5183: trailing whitespace.
source/configuration.rst:5189: trailing whitespace.
source/configuration.rst:5197: trailing whitespace.
source/configuration.rst:5282: trailing whitespace.
source/configuration.rst:5287: trailing whitespace.
source/configuration.rst:5288: trailing whitespace.
source/configuration.rst:5290: trailing whitespace.
source/configuration.rst:5291: trailing whitespace.
source/howto/source.rst:155: trailing whitespace.
source/howto/source.rst:158: trailing whitespace.
source/howto/source.rst:178: trailing whitespace.
source/howto/source.rst:180: trailing whitespace.
source/howto/source.rst:184: trailing whitespace.
source/howto/source.rst:187: trailing whitespace.
source/howto/source.rst:190: trailing whitespace.
source/howto/source.rst:192: trailing whitespace.
source/howto/source.rst:194: trailing whitespace.
source/howto/source.rst:196: trailing whitespace.
source/howto/source.rst:198: trailing whitespace.
source/howto/source.rst:200: trailing whitespace.
source/howto/source.rst:201: trailing whitespace.
source/howto/source.rst:744: trailing whitespace.
source/news/2024/index.rst:9: trailing whitespace.
source/news/2024/unit-1.32.0-released.rst:15: trailing whitespace.
source/news/2024/unit-1.32.0-released.rst:27: trailing whitespace.
source/news/2024/unit-1.32.0-released.rst:29: trailing whitespace.
source/news/2024/unit-1.32.0-released.rst:47: trailing whitespace.
source/news/2024/unit-1.32.0-released.rst:55: trailing whitespace.

@ac000
Copy link
Member

ac000 commented Feb 22, 2024

White space issue can be fixed via

$ git rebase --whitespace=fix master

@JTorreG
Copy link
Collaborator Author

JTorreG commented Feb 22, 2024

A couple of issues I see here

  1. Line lengths

I think we should stick to keeping our lines < 80 characters wide where possible, obviously commands, URL's etc should not be wrapped.

  1. White space damage

These patches introduce a fair amount of excess whitespace

$ git diff --check master.. | grep -v ^+ # because the highlighted whitespace won't show here

Trailing spaces slipped in when moving content from Confluence I will resolved those.

Line length is not an issue in my book. We don't enforce in any doc repos. We disable the checks in linter. We can discuss it and make a decision.

@callahad
Copy link
Collaborator

@lcrilly I responded to that over in #110 (comment) if you'd like to consider my rationale here

@JTorreG JTorreG merged commit cb83307 into master Feb 27, 2024
4 checks passed
@JTorreG JTorreG deleted the release-1.32 branch May 22, 2024 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants