You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SOLR-17979 Improve changes2html.py for authors and PR detection (#3831)
- Authors with url and github nick handled
- Plain PR ref `#123` detected as PR#123 with github link
- Correct a changelog yaml missing JIRA issue
- Fix links in dev-docs/changelog.adoc
- Describe logchangeArchive task.
- Remove mention of Perl as a requirement for build
Copy file name to clipboardExpand all lines: dev-docs/changelog.adoc
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ solr/
37
37
38
38
== 3. The YAML format
39
39
40
-
Below is an example of a changelog yaml fragment. The full yaml format is xref:https://logchange.dev/tools/logchange/reference/#tasks[documented here], but we normally only need `title`, `type`, `authors` and `links`. For a change without a JIRA, you can add the PR number in `issues`:
40
+
Below is an example of a changelog yaml fragment. The full yaml format is https://logchange.dev/tools/logchange/reference/#yaml-entry-format[documented here], but we normally only need `title`, `type`, `authors` and `links`. For a change without a JIRA, you can add the PR number in `issues`:
41
41
42
42
[source, yaml]
43
43
----
@@ -120,8 +120,13 @@ The logchange gradle plugin offers some tasks, here are the two most important:
120
120
121
121
| `logchangeRelease`
122
122
| Creates a new changelog release by moving files from `changelog/unreleased/` directory to `changelog/vX.Y.Z` directory
123
+
124
+
| `logchangeArchive`
125
+
| Archives the list of released versions up to (and including) the specified version by transferring their summaries to the `archive.md` file, merging all existing archives, and deleting the corresponding version directories.
123
126
|===
124
127
128
+
The `logchangeRelease` and `logchangeGenerate` tasks are used by ReleaseWizard. The `logchangeArchive` task can be ran once for every major release or when the number of versioned changelog folders grow too large.
129
+
125
130
These are integrated in the Release Wizard.
126
131
127
132
=== 6.2 Migration tool
@@ -242,5 +247,5 @@ Example report output (Json or Markdown):
242
247
243
248
== 7. Further Reading
244
249
245
-
* xref:https://github.com/logchange/logchange[Logchange web page]
Copy file name to clipboardExpand all lines: dev-docs/how-to-contribute.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ In order to make a new contribution to Solr you will use the fork you have creat
33
33
1. Create a new Jira issue in the Solr project: https://issues.apache.org/jira/projects/SOLR/issues
34
34
2. Create a new branch in your Solr fork to provide a PR for your contribution on the newly created issue. Make any necessary changes for the given bug/feature in that branch. You can use additional information in these dev-docs to build and test your code as well as ensure it passes code quality checks.
35
35
3. Once you are satisfied with your changes, get your branch ready for a PR by running `./gradlew tidy updateLicenses check -x test`. This will format your source code, update licenses of any dependency version changes and run all pre-commit tests. Commit the changes.
36
-
* Note: the `check` command requires `perl` and `python3` to be present on your `PATH` to validate documentation.
36
+
* Note: the `check` command requires `python3` to be present on your `PATH` to validate documentation.
37
37
4. Open a PR of your branch against the `main` branch of the apache/solr repository. When you open a PR on your fork, this should be the default option.
38
38
* The title of your PR should include the Solr Jira issue that you opened, i.e. `SOLR-12345: New feature`.
39
39
* The PR description will automatically populate with a pre-set template that you will need to fill out.
0 commit comments