-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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.5 #12680
Comments
I set the |
Nlog configurations have changed and there is no indication about it in the release.md file. We should advise people that the NLog configs have changed so that it doesn't lead to overlogging for them. https://github.com/NLog/NLog.Web/wiki/Missing-trace%5Cdebug-logs-in-ASP.NET-Core-6%3F |
Also need to update the Minor issue, but we tracked +1gb of logs this morning after deploying, because we rely on the aspnetcore logging section to reduce our log levels. |
Well, it can become a bigger issue if the logs are filling the entire server storage. So, everyone should make sure to take a look before deploying. |
It is also possible to overwite the default value using this static-property (apply before NLog.Web.NLogAspNetCoreOptions.Default.RemoveLoggerFactoryFilter = false; The recommended approach is just to fix the NLog-configuration like this: <rules>
<logger name="System.*" finalMinLevel="Warn" /> <!-- Insert at the top -->
<logger name="Microsoft.*" finalMinLevel="Warn" /> <!-- Insert at the top -->
<!-- Everything else -->
</rules> |
Prepare the project
Do some housekeeping on GitHub in the main repo.
Prepare the code
Update the source so everything looks like on the new version.
release/<version name>
branch out ofmain
.OrchardCore.ProjectTemplates
.OrchardCore.Commons.props
file: UpdateVersionPrefix
for release versions (like "1.0.0") andVersionSuffix
for pre-release versions (like "rc2", for the full version to be e.g. "1.0.0-rc2").ManifestConstants
.Prepare and publish Orchard Core Translations
Update everything in the Translations project. Only do this once all the code changes are done since localized strings can change until then.
OrchardCore.Translations.All
package reference in the main repo's src/OrchardCore.Build/Dependencies.props file to refer to the new NuGet package.Test the release
Make sure everything works all right.
Prepare the documentation
Update the docs so they contain information about the new release so once the release is out you'll just need to point to new information.
Publish the release
Do the harder parts of making the release public. This should come after everything above is done.
release/<version name>
tomaster
.master
need two approvals so you'll need to create a pull request.main
with the full version name, including the prefix and suffix (e.g. "1.0.0-rc2").Publicize the release
Let the whole world know about our shiny new release. Savor this part! These steps will make the release public so only do them once everything else is ready.
For details on this version see the [release notes in the documentation](link here).
). Add a link to this release under Status in the root README.The text was updated successfully, but these errors were encountered: