-
Couldn't load subscription status.
- Fork 81
Added mention about LTS updates in the update doc #2694
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If "Service portal" is a proper noun, it might deserve a capital each time. If not, there is an occurence with a cap needing lowercase.
| They update your service portal to match the new version. | ||
| This ensures that you receive notifications about new maintenance releases and security advisories for the correct version. | ||
| You can contact support at support@ibexa.co or through your [Support portal](https://support.ibexa.co). | ||
| You can contact support at support@ibexa.co or through your [Service portal](https://support.ibexa.co). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Capitalization inconsistency: Shouldn't "Service portal" be capitalized everywhere?
Co-authored-by: Tomasz Dąbrowski <64841871+dabrt@users.noreply.github.com>
|
@dabrt than you for your comments, I've applied all of them |
* Added mention about LTS updates * Support portal -> Service portal * Apply suggestions from code review Co-authored-by: Tomasz Dąbrowski <64841871+dabrt@users.noreply.github.com> * Update docs/resources/contributing/report_and_follow_issues.md * Unified occurances to "Service portal" --------- Co-authored-by: Tomasz Dąbrowski <64841871+dabrt@users.noreply.github.com>
Target: master, 4.6
It's been reported to me that not all Partners are aware that LTS Updates need to be updated separately - so I'm adding a mention about it at the end of the update doc.
Things done in addition:
Both points consulted with @mateuszbieniek