This is an automated email from the ASF dual-hosted git repository.
hansva pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hop.git
The following commit(s) were added to refs/heads/master by this push:
new 07d19586c1 #1923: move references from Jira to GitHub
new 388ae64bda Merge pull request #1924 from hansva/master
07d19586c1 is described below
commit 07d19586c14702e72c7446c47ddb577c07e2c00d
Author: Hans Van Akelyen <[email protected]>
AuthorDate: Wed Dec 7 11:10:13 2022 +0100
#1923: move references from Jira to GitHub
---
CONTRIBUTING.md | 4 ++--
README.md | 4 ++--
assemblies/static/src/main/resources/README.txt | 2 +-
.../modules/ROOT/pages/apache-release/creating-a-release.adoc | 2 +-
docs/hop-dev-manual/modules/ROOT/pages/integration-testing.adoc | 2 +-
docs/hop-dev-manual/modules/ROOT/pages/internationalisation.adoc | 2 +-
docs/hop-dev-manual/modules/ROOT/pages/setup-dev-environment.adoc | 8 ++++----
.../modules/ROOT/pages/hop-vs-kettle/if-you-know-kettle.adoc | 2 +-
.../beam-dataflow-pipeline-engine.adoc | 2 +-
.../ROOT/pages/pipeline/transforms/beamkinesisconsume.adoc | 2 +-
.../ROOT/pages/pipeline/transforms/beamkinesisproduce.adoc | 2 +-
pom.xml | 4 ++--
12 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 40fefcbeed..af853f4fe0 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -23,7 +23,7 @@ Apache Hop is developed by an open and friendly community.
Everybody is cordiall
## What do you want to do?
Contributing to Hop goes beyond writing code for the project. Below, we list
different opportunities to help the project:
-* To report a problem with Hop, open a Hop's
[jira](https://issues.apache.org/jira/projects/HOP/issues), log in if
necessary, and click on the "+" in the left side bar (Shortcut "c").
+* To report a problem with Hop, open a Hop's [GitHub
Issue](https://github.com/apache/hop/issues), log in if necessary, and click on
the "+" in the left side bar (Shortcut "c").
Please give detailed information about the problem you encountered and, if
possible, add a description that helps to reproduce the problem. For more
information go to our
[info](https://hop.apache.org/community/contribution-guides/jira-guide/) page.
* Read the [Code Contribution
Guide](https://hop.apache.org/community/contribution-guides/code-contribution-guide/)
* Help With Code Reviews [Code Review
Guide](https://hop.apache.org/community/contribution-guides/code-review-guide/)
@@ -33,7 +33,7 @@ Please give detailed information about the problem you
encountered and, if possi
* Support Hop Users
* Join us on our [Mattermost](https://chat.project-hop.org/) server and
answer questions
* Reply to Hop related questions on Stack Overflow with the hop tag or the
Hop forums
- * Check the latest issues in Jira for tickets which are actually user
questions
+ * Check the latest issues in GtiHub Issues for tickets which are actually
user questions
* Improve the Website [Website Contribution
Guide](https://hop.apache.org/community/contribution-guides/website-contribution-guide/)
* Spread the Word about Hop
* Organize or attend a Hop Meetup
diff --git a/README.md b/README.md
index 2115b50f0b..0cc026a10f 100644
--- a/README.md
+++ b/README.md
@@ -35,7 +35,7 @@ Your help is invaluable.
There are various things you can do to help Hop continue moving forward
quickly:
-- Log bugs, request features in the [Hop
JIRA](https://issues.apache.org/jira/projects/HOP)
+- Log bugs, request features in [GitHub](https://github.com/apache/hop/issues)
- Ask questions in the [mailing
lists](https://hop.apache.org/community/mailing-list/)
or [mattermost](https://chat.project-hop.org/hop/channels/dev)
- Help us write or fix documentation (lot of opportunities)
@@ -110,7 +110,7 @@ After a successful build, the Hop UI can be started.
On Windows, run `hop-gui.bat`, on Mac and Linux, run `hop-gui.sh`
-Help us to improve Hop by logging issues in the [Hop
JIRA](https://issues.apache.org/jira/projects/HOP)
+Help us to improve Hop by logging issues in [GitHub
Issues](https://github.com/apache/hop/issues)
This distribution includes cryptographic software. The country in which you
currently reside may have restrictions on
the import, possession, use, and/or re-export to another country, of
encryption software. BEFORE using any encryption
diff --git a/assemblies/static/src/main/resources/README.txt
b/assemblies/static/src/main/resources/README.txt
index 4ea2e69713..221bcf905b 100644
--- a/assemblies/static/src/main/resources/README.txt
+++ b/assemblies/static/src/main/resources/README.txt
@@ -15,7 +15,7 @@
* limitations under the License.
*/
-When finding issues please log a bug in our public Jira
https://issues.apache.org/jira/projects/HOP
+When finding issues please log a bug in GitHub
https://github.com/apache/hop/issues
When you have a question you can use our mailing list
(http://hop.apache.org/community/mailing-list/) or Mattermost Chat
(https://chat.project-hop.org/hop/channels/dev)
diff --git
a/docs/hop-dev-manual/modules/ROOT/pages/apache-release/creating-a-release.adoc
b/docs/hop-dev-manual/modules/ROOT/pages/apache-release/creating-a-release.adoc
index 4681cf4c43..b78c74c6f3 100644
---
a/docs/hop-dev-manual/modules/ROOT/pages/apache-release/creating-a-release.adoc
+++
b/docs/hop-dev-manual/modules/ROOT/pages/apache-release/creating-a-release.adoc
@@ -223,7 +223,7 @@ Release artifacts are signed with the following key:
<ADD URL TO YOUR KEY ON A PUBLIC KEYSERVER>
For more information about the contents of this release, see:
-<ADD URL TO RELEASE IN JIRA>
+<ADD URL TO RELEASE IN GITHUB>
Please vote on releasing this package as Apache Hop X.XX!
diff --git a/docs/hop-dev-manual/modules/ROOT/pages/integration-testing.adoc
b/docs/hop-dev-manual/modules/ROOT/pages/integration-testing.adoc
index bb1dda9d00..96546e9cd1 100644
--- a/docs/hop-dev-manual/modules/ROOT/pages/integration-testing.adoc
+++ b/docs/hop-dev-manual/modules/ROOT/pages/integration-testing.adoc
@@ -58,7 +58,7 @@ image::integration-tests-004.png[]
. create a unit test
+
Now you can add your own workflow to the project folder.
-Make sure you have a Jira ticket you can refer to when creating a pull request.
+Make sure you have a GitHub Issue number you can refer to when creating a pull
request.
== Adding a new project
diff --git a/docs/hop-dev-manual/modules/ROOT/pages/internationalisation.adoc
b/docs/hop-dev-manual/modules/ROOT/pages/internationalisation.adoc
index 9126355de5..2dcbe7a094 100644
--- a/docs/hop-dev-manual/modules/ROOT/pages/internationalisation.adoc
+++ b/docs/hop-dev-manual/modules/ROOT/pages/internationalisation.adoc
@@ -190,7 +190,7 @@ image::hop-translator-save-files-dialog.png[Hop Translator:
the save files dialo
Once the files are saved you re-build Hop and test them by using the
translated keys.
Finally, don't forget to commit and push changes as described here:
xref:setup-dev-environment.adoc[Setting up your development environment]
-Please reference a JIRA case and see if there aren't any already for the
locale you're covering.
+Please reference a Github Issue and see if there aren't any already for the
locale you're covering.
=== Highlighting codes
diff --git a/docs/hop-dev-manual/modules/ROOT/pages/setup-dev-environment.adoc
b/docs/hop-dev-manual/modules/ROOT/pages/setup-dev-environment.adoc
index db016a2b29..cc7de0e4b3 100644
--- a/docs/hop-dev-manual/modules/ROOT/pages/setup-dev-environment.adoc
+++ b/docs/hop-dev-manual/modules/ROOT/pages/setup-dev-environment.adoc
@@ -178,16 +178,16 @@ You can now set breakpoints in your code and see what's
going on.
== Committing work
Updating your fork can be done simply by committing locally and then pushing
those changes to "origin".
-Make sure to always reference a HOP-xxxxx JIRA case!
+Make sure to always reference a #12345 GitHub issue!
For example:
[source]
-git commit -m "HOP-98765 : My work description" .
+git commit -m "#12345 : My work description" .
== Updating your fork
After a while it's likely your "origin" fork will be lagging behind with the
main "upstream" Hop codebase.
-You can develop against the ```master``` branch of the codebase or you can
create different branches for the features you're building or the JIRA cases
you're fixing.
+You can develop against the ```master``` branch of the codebase or you can
create different branches for the features you're building or the GitHub issue
you're fixing.
In the commands below we assume you want to update your ```master``` branch.
If this is not the case, replace ```master``` with the branch you're
interested in and later want to generate a pull request for.
@@ -227,7 +227,7 @@ If all goes well you should see something like the
following:
image::github-create-pull-request.png[]
After you hit the green "Create pull request" button you will be presented
with the opportunity to describe the changes.
-Make sure to reference the right JIRA cases and leave useful tips for the
reviewers of the changes.
+Make sure to reference the right GitHub Issue and leave useful tips for the
reviewers of the changes.
Again: as mentioned above *please make sure your project builds and all tests
succeed.*
Once you created the pull request we will run all sorts of tests and this will
take some time.
diff --git
a/docs/hop-tech-manual/modules/ROOT/pages/hop-vs-kettle/if-you-know-kettle.adoc
b/docs/hop-tech-manual/modules/ROOT/pages/hop-vs-kettle/if-you-know-kettle.adoc
index 23b443e2d7..a24ce202ab 100644
---
a/docs/hop-tech-manual/modules/ROOT/pages/hop-vs-kettle/if-you-know-kettle.adoc
+++
b/docs/hop-tech-manual/modules/ROOT/pages/hop-vs-kettle/if-you-know-kettle.adoc
@@ -25,7 +25,7 @@ under the License.
Hop wants to allow data engineers to be able to deliver high quality work,
deliver that work fast and integrated with bleeding edge technology.
-We want Hop to be completely open source, and are eager to hear your feedback
on our https://chat.project-hop.org[chat] and just as eager to see your bug
tickets and feature request in
https://issues.apache.org/jira/projects/HOP/issues[JIRA].
+We want Hop to be completely open source, and are eager to hear your feedback
on our https://chat.project-hop.org[chat] and just as eager to see your bug
tickets and feature request in https://github.com/apache/hop/issues[Github
Issues].
As an open source first project, we started the https://www.apache.org/[Apache
Software Foundation] https://incubator.apache.org/[incubation] process in
September 2020 and graduated as and ASF https://projects.apache.org/[top level
project] in December 2021.
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/beam-dataflow-pipeline-engine.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/beam-dataflow-pipeline-engine.adoc
index 6b2337fb11..c8ba80c354 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/beam-dataflow-pipeline-engine.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/beam-dataflow-pipeline-engine.adoc
@@ -146,4 +146,4 @@ To allow encrypted (TLS) network connections to, for
example, Kafka and Neo4j Au
This is done by setting security property `jdk.tls.disabledAlgorithms` to
value: `Lv3, RC4, DES, MD5withRSA, DH keySize < 1024, EC keySize < 224,
3DES_EDE_CBC, anon, NULL`.
Please let us know if you have a need to make this configurable and we'll look
for a way to not hardcode this.
-Just create a JIRA case to let us know.
+Just create a Github Issue to let us know.
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/beamkinesisconsume.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/beamkinesisconsume.adoc
index a5ace1cfb4..aa65bb1d2c 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/beamkinesisconsume.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/beamkinesisconsume.adoc
@@ -39,7 +39,7 @@ The Beam link:https://aws.amazon.com/kinesis/[Kinesis]
Consume transform consume
== Limitations
-The main limitation of the Kinesis consumer is that it currently only supports
reading String messages. Please create a request in JIRA if you want to see
support for Avro messages and other formats.
+The main limitation of the Kinesis consumer is that it currently only supports
reading String messages. Please create a request in GitHub if you want to see
support for Avro messages and other formats.
== Options
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/beamkinesisproduce.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/beamkinesisproduce.adoc
index 5b3ac9212d..ae9189caf4 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/beamkinesisproduce.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/beamkinesisproduce.adoc
@@ -39,7 +39,7 @@ The Beam link:https://aws.amazon.com/kinesis/[Kinesis]
Produce transform sends d
== Limitations
-The main limitation of the Kinesis produce transform is that it currently only
supports sending String data. Please create a request in JIRA if you want to
see support for Avro messages and other formats.
+The main limitation of the Kinesis produce transform is that it currently only
supports sending String data. Please create a request in GitHub if you want to
see support for Avro messages and other formats.
== Options
diff --git a/pom.xml b/pom.xml
index e2d164d9b1..5aa603093d 100644
--- a/pom.xml
+++ b/pom.xml
@@ -65,8 +65,8 @@
</mailingLists>
<issueManagement>
- <system>JIRA</system>
- <url>https://issues.apache.org/jira/browse/HOP</url>
+ <system>GitHub Issues</system>
+ <url>https://github.com/apache/hop/issues</url>
</issueManagement>
<ciManagement>
<system>Jenkins</system>
