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

#1731 Docs for 20.0 release #1754

Merged
merged 48 commits into from
Oct 26, 2023
Merged

#1731 Docs for 20.0 release #1754

merged 48 commits into from
Oct 26, 2023

Conversation

raman-m
Copy link
Member

@raman-m raman-m commented Oct 24, 2023

Fixes #1731

This is the major update of the documentation for the current 20.0 release.

Proposed Changes

  • Reviewed all features, pages in .rst files
  • Updated links & features to meet requirements of 20.0 release
  • Updated README.md which looks better and modern now
  • Reviewed development process aka Release Process
  • Added Future subsections to say about team plans

I guess, most interesting things to look at are:

Review doc. Update by links. Add labels.
@raman-m raman-m self-assigned this Oct 24, 2023
@raman-m raman-m added documentation Needs a documentation update release Pre/Release (minor, major) labels Oct 24, 2023
@raman-m raman-m requested a review from RaynaldM October 24, 2023 20:16
@raman-m
Copy link
Member Author

raman-m commented Oct 24, 2023

@ggnaegi FYI
The Coveralls.io badge will be hidden on README page until we fix this. 😋

Do you approve this? Something else?

@ggnaegi
Copy link
Member

ggnaegi commented Oct 24, 2023

@ggnaegi FYI
The Coveralls.io badge will be hidden on README page until we fix this. 😋

Do you approve this? Something else?

Yes, until we introduce sonarqube 😊

@raman-m
Copy link
Member Author

raman-m commented Oct 25, 2023

@ggnaegi Do you approve?
We're very close to releasing v 20.0.1 with this docs.
As a rest of work, I need to add make.bash to have ability to build docs on Linux machines. Current make.bat allows to build docs on Windows machine only.

@ggnaegi
Copy link
Member

ggnaegi commented Oct 25, 2023

@ggnaegi Do you approve?
We're very close to releasing v 20.0.1 with this docs.
As a rest of work, I need to add make.bash to have ability to build docs on Linux machines. Current make.bat allows to build docs on Windows machine only.

@raman-m Sounds good to me. Why "-" instead of "^" ?

@raman-m
Copy link
Member Author

raman-m commented Oct 25, 2023

@ggnaegi commented
Sounds good to me. Why "-" instead of "^" ?

  • = for sections
  • - for subsections
  • ^ for subsubsections

All features have been defined as sections with =, and some pages had the next level ^ (subsubsections), which is wrong because the next sublevel after sections is - (subsections).

More here: reST Sections

@ggnaegi
Copy link
Member

ggnaegi commented Oct 25, 2023

Ok, reviewing the docs :-)

I would be up for the GraphQL bit, but with https://github.com/ChilliCream/graphql-platform, not graphql.net.

I have some experience with HotChocolate, since I implemented GraphQL for a customer.

this .net server is imho better and Michael (the owner) is a member of the GraphQL Technical Steering Committee.

But that's my opinion.

Copy link
Member

@ggnaegi ggnaegi left a comment

Choose a reason for hiding this comment

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

Great job! I have written two comments, but we should send a positive message to the contributors.


You must set a number greater than 0 against ExceptionsAllowedBeforeBreaking for this rule to be implemented. Duration of break means the circuit breaker will stay open for 1 second after it is tripped.
TimeoutValue means if a request takes more than 5 seconds it will automatically be timed out.
You must set a number greater than ``0`` against **ExceptionsAllowedBeforeBreaking** for this rule to be implemented.
Copy link
Member

Choose a reason for hiding this comment

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

Here I would mention that the functionality is not working at the minute (see ticket).

Copy link
Member Author

Choose a reason for hiding this comment

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

Which one?

Copy link
Member Author

Choose a reason for hiding this comment

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

If we have a bug in backlog, it doesn't mean we have to remove docs, right?
Make sense?

Copy link
Member Author

Choose a reason for hiding this comment

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

Or, would you like to mention this bug in docs?
Won't it be strange?

Copy link
Member Author

Choose a reason for hiding this comment

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

I have an idea to mark this feature by special label and redirect users to look at current issues? Souds good? Sounds like a fix of this code review issue?
For example we have label: Websockets label for Websockets feature.

Copy link
Member

Choose a reason for hiding this comment

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

Yes, great idea!

Copy link
Member Author

@raman-m raman-m Oct 25, 2023

Choose a reason for hiding this comment

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

I found it! It is #1550

@ggnaegi I've added special QoS label, and added the reference to QoS footnote in the doc
Fixed in 88fbd1d

All NuGet package builds & releases are done with CircleCI `here <https://circleci.com/gh/ThreeMammals>_` and all releases are done from `here <https://ci.appveyor.com/project/TomPallister/ocelot-ayj4w>_`.
All NuGet package builds and releases are done with CircleCI, see `Pipelines - ThreeMammals/Ocelot <https://circleci.com/gh/ThreeMammals/Ocelot/>`_.

Only Tom Pallister (owner) and Ocelot Core Team members (maintainers) can merge releases into **main** at the moment.
Copy link
Member

Choose a reason for hiding this comment

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

This is a very negative way of explaining things. I wouldn't tell the contributors about the organizational details, and instead of writing "Do not mention Tom", I would use "Please, mention Raman".

Copy link
Member Author

Choose a reason for hiding this comment

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

Good point! We need to be more pleasant maintainers. 🤣
I would prefer to replace Do not mention Tom line by another phrase: "We do follow this dev and release process... bla-bla-bla"

Copy link
Member Author

@raman-m raman-m Oct 25, 2023

Choose a reason for hiding this comment

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

As Tom wrote a lot in docs, I would say If you need to do something which we won't do, please help yourself! 🤣

And, relevant version:
If you reference Tom in issues to help, who is not going to reply to you, please help yourself! 🤣

Copy link
Member Author

@raman-m raman-m Oct 25, 2023

Choose a reason for hiding this comment

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

✔️ Fixed in f9f6d8d
Are we pleasant now, @ggnaegi ?

@raman-m
Copy link
Member Author

raman-m commented Oct 25, 2023

@ggnaegi commented
I would be up for the GraphQL bit, but with https://github.com/ChilliCream/graphql-platform, not graphql.net.

I am not a fun to integrate custom libraries, except direct references to official libs.
Let's discuss GraphQl later, plz!

@ggnaegi
Copy link
Member

ggnaegi commented Oct 25, 2023

@ggnaegi commented
I would be up for the GraphQL bit, but with https://github.com/ChilliCream/graphql-platform, not graphql.net.

I am not a fun to integrate custom libraries, except direct references to official libs.
Let's discuss GraphQl later, plz!

Mmh. Graphql.NET is not the official implementation by the way. There is no official implementation.

@raman-m
Copy link
Member Author

raman-m commented Oct 25, 2023

@ggnaegi left a code review comment:
Great job!

Thanks!

I have written two comments, but we should send a positive message to the contributors.

I've fixed issues! Please, approve, if no other issues.

@raman-m raman-m requested a review from ggnaegi October 25, 2023 11:00
@raman-m
Copy link
Member Author

raman-m commented Oct 25, 2023

@RaynaldM Hey, Ray!
One more approval please!

Copy link
Member

@ggnaegi ggnaegi left a comment

Choose a reason for hiding this comment

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

Ok for me, thanks!

@raman-m
Copy link
Member Author

raman-m commented Oct 26, 2023

@RaynaldM Good morning, France! 😊

@raman-m raman-m merged commit 640b005 into release/20.0 Oct 26, 2023
2 checks passed
@raman-m raman-m deleted the release/20.0-docs branch October 26, 2023 11:08
raman-m added a commit that referenced this pull request Oct 27, 2023
Documentation release 20.0.1
--------------------------------

Guillaume Gnaegi (1):
      #1731 Read the Docs configuration file v2 (#1733)

Raman Maksimchuk (1):
      #1731 Docs for 20.0 release (#1754)

raman-m (2):
      Prepare for the 20.0.1 release
      Trigger new build...
ibnuda pushed a commit to ibnuda/Ocelot that referenced this pull request Nov 8, 2023
* Update README.md

Review doc. Update by links. Add labels.

* Update readme.md: Review doc. Update links

* Update building.rst: Review doc

* Update overview.rst

* Update tests.rst: Review doc. Update links

* Update releaseprocess.rst: Update development process

* Update bigpicture.rst: Copy Welcoming from README

* Update contributing.rst: Add discussions and dev process refs

* Update gettingstarted.rst

* Update gotchas.rst: Write IIS gotchas

* Update notsupported.rst: Add sections. Use more links

* Update administration.rst: Review doc. Fix markup. More links

* Update authentication.rst: Review doc. Add more links

* Update authorization.rst: review. Add "Authorization Middleware" section

* Update caching.rst: Review markup. More links

* Update claimstransformation.rst: Review doc. Update markdown. Middleware links

* Correct spelling error  in dev docs

* Update configuration.rst: Review the doc. Rewrite "SSL Errors" section

* Update delegatinghandlers.rst: Review. More links. Add "Order of Execution" section

* Update dependencyinjection.rst: Review the doc. Fix markdown

* Update errorcodes.rst: Review. Add "Design" section

* Update graphql.rst: Review. Add "Future" section

* Update headerstransformation.rst: Review. More links. Rewrite Placeholders & Future sections

* Update headerstransformation.rst: Add "Global Headers Transformation" subsection

* Update kubernetes.rst: Review. Links. Add K8s logo

* Update kubernetes.rst: Add link to the parent feature

* Update loadbalancer.rst: Fix markdown. More links

* Update logging.rst: More links. Rewrite "Warning" section

* Update methodtransformation.rst

* Update middlewareinjection.rst: Review. Check links. Add "Future" section

* Update qualityofservice.rst: Review markdown

* Update ratelimiting.rst: Review. Markdown. Add "Future" section

* Update requestaggregation.rst: Review. Fix markdown

* Update requestid.rst: Review markdown

* Update routing.rst: Review markdown. Simplify code blocks

* Update servicediscovery.rst: Review markdown

* Update servicefabric.rst: Review markdown

* Update tracing.rst: Review markdown. More links

* Update websockets.rst: Complete rewrite

* Update README.md: Hide Coverage badge. More footnotes

* Update README.md: Add "Service Discovery" footnote

* Update index.rst: Arrange features. More instructions

* Update releaseprocess.rst: Be more pleasant

* Update qualityofservice.rst: Add QoS label and footnote

* Fix Sphinx build errors & warning. Fix typos

* Add bash script

* Order feature names ascending

* Sync & update scripts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Needs a documentation update release Pre/Release (minor, major)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to generate documentation on ReadTheDocs
2 participants