-
Notifications
You must be signed in to change notification settings - Fork 189
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
Update Telescope Overview with Release 3.0 Information #3739
Comments
@sirinoks Hi Alex, I know you did a lot of the documentation and projects for release 3.0. Would there be a best resource to gather all of this to add into the documentation here? |
@AmasiaNalbandian There isn't a single place to look currently, which makes me want to solve this for the future generation.. If you want to meet in some call, or start a discussion to arrange all the topics and areas, I'm down. This will be needed anyway, since we need a "map of microservices" for docusaurus. Collecting such information would greatly help in this specific issue. I can give you an overview of the things I know myself, but it will not be complete. PS: Perhaps for the next generation, after each week's triages, there should be a specific task to complete - in notes, or to add to notes - just update the docusaurus file with what was added. And after a release - review what was added and make it look nicer..? |
At this point I think it'll be hard for just one person to summarize what we did since we had a rather large group. I can list some of the things I remember, and obviously there's a lot of other stuff, but hopefully it'll help.
(I'll add more if I remember some later on) |
Where is the problem?
What exactly is wrong:
When you go to the document webpage you see the area for release 3.0, however, there is no information on what happened in release 3.0 - which has come and gone.
What should it be instead:
We need to update this section to include the changes made in release 3.0.
There's a few other places we need to add more information regarding release 3.0
The text was updated successfully, but these errors were encountered: