[UIMA-6436] Move maintainer documentation from website into maintainer guide #197
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…r guide - Added an initial maintainer guide with release instructions and trying if this can be published via Jenkins
…r guide - Add maintainer one-time-setup page - Try having the CSS file separate instead of inlining it
…r guide - Formatting
…r guide - Disable publishing HTML again because we do it via a separate Jenkins job now
…ntation-from-website-into-maintainer-guide * main: (23 commits) [NO JIRA] Set version to 3.4.0-SNAPSHOT [NO JIRA] Set version to 3.4.0-SNAPSHOT [UIMA-6440] Stage release artifacts as part of the build [UIMA-6440] Stage release artifacts as part of the build [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release uimaj-3.3.0 [NO-JIRA] Add license header to script. [NO-JIRA] Added a little release helper script [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release uimaj-3.3.0 [UIMA-6374] Create CAS (de)serialization test suite [UIMA-6395] Apache UIMA Java SDK 3.3.0 release [UIMA-6395] Apache UIMA Java SDK 3.3.0 release [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release uimaj-3.3.0 [UIMA-6395] Apache UIMA Java SDK 3.3.0 release [maven-release-plugin] rollback the release of uimaj-3.3.0 [maven-release-plugin] prepare release uimaj-3.3.0 [UIMA-6395] Apache UIMA Java SDK 3.3.0 release [UIMA-6395] Apache UIMA Java SDK 3.3.0 release ...
…r guide - Add section on project structure
…ntation-from-website-into-maintainer-guide * main: [UIMA-6454] Update dependencies (UIMA Java SDK 3.3.1)
…ntation-from-website-into-maintainer-guide
…r guide * Add documentation for auto-staging and generating Jira change reports * Add information how to avoid having to update the `jiraVersion` property of every release and deprecate the step in the checklist
…r guide * Deprecate outdated release steps e.g. related to the old way of doing Eclipse update sites
…r guide * Provide tips on signature and hash validation * Provide tips on additional release quality checking
…r guide * Additional explanations on signature and checksum checking
…r guide * Nicer links
…ntation-from-website-into-maintainer-guide
…r guide * Update command for signature validation * Remove stage-release-artifacts.sh which has been superseded by the auto-staging mechanism
…r guide * Update commands for checksum validation
…r guide * Add note that credentials are required for auto-staging
…r guide * Improve commands for checking signatures and hashes * Use svn export instead of svn checkout to avoid having a `.svn` folder which is annoying for auto-checking signatures and hashes
…r guide * Add section on Maven toolchains
…ntation-from-website-into-maintainer-guide * main: [UIMA-6462] Avoid deploy broken checksum files for p2content.xml and artifacts.xml in feature modules
…r guide * Fix module version
…ntation-from-website-into-maintainer-guide
…r guide * Missing license header
reckart
deleted the
refactoring/UIMA-6436-Move-maintainer-documentation-from-website-into-maintainer-guide
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JIRA Ticket: https://issues.apache.org/jira/browse/UIMA-6436
What's in the PR
How to test manually
Automatic testing
Documentation
Organizational
Only dependencies under approved licenses are allowed. LICENSE and NOTICE files in the respective modules where dependencies have been added as well as in the project root have been updated.