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-website.git
The following commit(s) were added to refs/heads/master by this push:
new 2ed2971b6 Remove links to Jira
new f1415bb6b Merge pull request #178 from hansva/master
2ed2971b6 is described below
commit 2ed2971b6a27f72e3489057ba32b0d53a72b9e56
Author: Hans Van Akelyen <[email protected]>
AuthorDate: Fri Dec 9 14:12:01 2022 +0100
Remove links to Jira
---
.asf.yaml | 1 -
antora-ui-hop/src/partials/footer-content.hbs | 2 +-
content/community/contributing.adoc | 6 ++--
.../code-contribution-guide.adoc | 36 +++++++++++-----------
.../contribution-guides/code-review-guide.adoc | 12 ++++----
.../documentation-contribution-guide.adoc | 6 ++--
.../{jira-guide.adoc => github-guide.adoc} | 28 ++++++-----------
.../website-contribution-guide.adoc | 6 ++--
content/community/support.adoc | 2 +-
content/community/tools.adoc | 14 +++------
layouts/partials/footer.html | 2 +-
static/doap_Hop.rdf | 8 ++---
12 files changed, 53 insertions(+), 70 deletions(-)
diff --git a/.asf.yaml b/.asf.yaml
index 20fc58a49..3160df52e 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -18,7 +18,6 @@
notifications:
pullrequests: [email protected]
commits: [email protected]
- jira_options: link label comment
publish:
whoami: asf-site
diff --git a/antora-ui-hop/src/partials/footer-content.hbs
b/antora-ui-hop/src/partials/footer-content.hbs
index 6352cec88..ab1ffb0cb 100644
--- a/antora-ui-hop/src/partials/footer-content.hbs
+++ b/antora-ui-hop/src/partials/footer-content.hbs
@@ -7,7 +7,7 @@
</dl>
<dl>
<dt>Community</dt>
- <dd><a target="_blank"
href="https://issues.apache.org/jira/projects/HOP/issues";>Jira</a></dd>
+ <dd><a target="_blank"
href="https://github.com/apache/hop/issues";>Github Issues</a></dd>
<dd><a target="_blank" href="https://chat.project-hop.org";>Chat</a></dd>
<dd><a target="_blank"
href="{{siteRootPath}}/community/team/">Team</a></dd>
</dl>
diff --git a/content/community/contributing.adoc
b/content/community/contributing.adoc
index 8ca1026f6..cd02f87fc 100644
--- a/content/community/contributing.adoc
+++ b/content/community/contributing.adoc
@@ -11,8 +11,8 @@ Contributing to Hop goes beyond writing code for the project.
Below, we list dif
[width="100%", ,cols="3,10", options="header,footer"]
|============================
|Area |Further Information
-|Report a Bug|To report a problem with Hop, open Hop’s
https://issues.apache.org/jira/projects/HOP/issues[Jira ,window=_blank], 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 link:../contribution-guides/jira-guide/[info] page.
+|Report a Bug|To report a problem with Hop, open Hop’s
https://github.com/apache/hop/issues[GitHub Issues ,window=_blank], 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 link:../contribution-guides/github-guide/[info] page.
|Contribute Code|Read the
link:../contribution-guides/code-contribution-guide/[Code Contribution Guide]
|Help With Code Reviews|Read the
link:../contribution-guides/code-review-guide/[Code Review Guide]
|Help Prepare a Release|Read the
link:../contribution-guides/release-contribution-guide/[Release Review Guide]
@@ -23,7 +23,7 @@ Please give detailed information about the problem you
encountered and, if possi
- 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 GitHub for tickets which are actually user
questions
|Improve the Website|Read the
link:../contribution-guides/website-contribution-guide/[Website Contribution
Guide]
|Spread the Word about Hop|
diff --git a/content/community/contribution-guides/code-contribution-guide.adoc
b/content/community/contribution-guides/code-contribution-guide.adoc
index 716f57943..addba678c 100644
--- a/content/community/contribution-guides/code-contribution-guide.adoc
+++ b/content/community/contribution-guides/code-contribution-guide.adoc
@@ -4,13 +4,13 @@ title: "Code Contribution Guide"
Apache Hop is maintained, improved, and extended by code contributions of
volunteers. We welcome contributions to Hop, but due to the size of the project
and to preserve the high quality of the code base, we follow a contribution
process that is explained in this document.
-*Please feel free to ask questions at any time*. Either send a message in the
dev channel on our chatserver or comment on the Jira issue you are working on.
+*Please feel free to ask questions at any time*. Either send a message in the
dev channel on our chatserver or comment on the GitHub issue you are working on.
*IMPORTANT*: Please read this document carefully before starting to work on a
code contribution. Follow the process and guidelines explained below.
Contributing to Apache Hop does not start with opening a pull request. We
expect contributors to reach out to us first to discuss the overall approach
together. Without consensus with the Hop committers, contributions might
require substantial rework or will not be reviewed.
<<code-contribution-process>>
[%hardbreaks]
-. <<create-jira-ticket, Create JIRA Ticked and Reach Consensus>>
+. <<create-github-issue, Create GitHub Issue and Reach Consensus>>
. <<implement-change, Implement Your Change>>
. <<open-pull-request, Open a Pull Request>>
. <<merge-change, Merge Change>>
@@ -18,16 +18,16 @@ Apache Hop is maintained, improved, and extended by code
contributions of volunt
.Contribution Process Table
[width="100%", cols="4"]
|====
-|[very big]*1 <<create-jira-ticket, Discuss>>*
+|[very big]*1 <<create-github-issue, Discuss>>*
-Create a https://issues.apache.org/jira/projects/HOP/issues[Jira] ticket or
mailing list discussion and reach consensus
+Create a https://github.com/apache/hop/issues[GitHub Issue] or mailing list
discussion and reach consensus
Agree on importance, relevance, scope of the ticket, discuss the
implementation approach and find a committer willing to review and merge the
change.
-*Only committers can assign a Jira ticket.*
+*Only committers can assign a GitHub Issues.*
|[very big]*2 <<implement-change, Implement>>*
-Implement the change according to the Code Style and Quality Guide and the
approach agreed upon in the Jira ticket.
+Implement the change according to the Code Style and Quality Guide and the
approach agreed upon in the ticket.
*Only start working on the implementation if there is consensus on the
approach (e.g. you are assigned to the ticket)*
@@ -35,7 +35,7 @@ Implement the change according to the Code Style and Quality
Guide and the appro
Open a pull request and work with the reviewer.
-*Pull requests belonging to unassigned Jira tickets or not authored by
assignee will not be reviewed or merged by the community.*
+*Pull requests belonging to unassigned GitHub Issues or not authored by
assignee will not be reviewed or merged by the community.*
|[very big]*4 <<merge-change, Merge>>*
@@ -45,16 +45,16 @@ A committer of Hop checks if the contribution fulfills the
requirements and merg
[frame=topbot]
|===
-|Note: trivial hot fixes such as typos or syntax errors can be opened as a
[hotfix] pull request, without a Jira ticket.
+|Note: trivial hot fixes such as typos or syntax errors can be opened as a
[hotfix] pull request, without a ticket.
|===
anchor:code-contribution-process[Code Contribution Process]
-== anchor:create-jira-ticket[]Create JIRA Ticket and Reach Consensus
+== anchor:create-github-issue[]Create GitHub Issue and Reach Consensus
The first step for making a contribution to Apache Hop is to reach consensus
with the Hop community. This means agreeing on the scope and implementation
approach of a change.
-In most cases, the discussion should happen in Hop’s bug tracker:
https://issues.apache.org/jira/projects/HOP/issues[Jira].
+In most cases, the discussion should happen in Hop’s bug tracker:
https://github.com/apache/hop/issues[GitHub].
The following types of changes require a discussion in the dev
https://chat.project-hop.org[chat] channel:
@@ -62,9 +62,9 @@ The following types of changes require a discussion in the
dev https://chat.proj
- potentially controversial changes or issues
- changes with very unclear approaches or multiple equal approaches
-Do not open a Jira ticket for these types of changes before the discussion has
come to a conclusion. Jira tickets based on a dev@ discussion should summarize
the outcome of that discussion.
+Do not open a GitHub Issues for these types of changes before the discussion
has come to a conclusion. GitHub Issues based on a dev@ discussion should
summarize the outcome of that discussion.
-*Requirements for a Jira ticket to get consensus:*
+*Requirements for a ticket to get consensus:*
- Formal requirements
* The _Title_ describes the problem concisely.
@@ -85,23 +85,23 @@ Do not open a Jira ticket for these types of changes before
the discussion has c
* Impact on Hop’s build time
* Dependencies and their licenses
-If a change is identified as a large or controversial change in the discussion
on Jira, it might require a Hop Improvement Proposal (HIP) or a discussion in
the dev channel to reach agreement and consensus.
+If a change is identified as a large or controversial change in the discussion
on GitHub, it might require a Hop Improvement Proposal (HIP) or a discussion in
the dev channel to reach agreement and consensus.
Contributors can expect to get a first reaction from a committer within a few
days after opening the ticket. If a ticket doesn’t get any attention, we
recommend reaching out to the developer chat. Note that the Hop community
sometimes does not have the capacity to accept all incoming contributions.
Once all requirements for the ticket are met, a committer will assign somebody
to the Assignee field of the ticket to work on it. Only committers have the
permission to assign somebody.
-*Pull requests belonging to unassigned Jira tickets will not be reviewed or
merged by the community.*
+*Pull requests belonging to unassigned tickets will not be reviewed or merged
by the community.*
== anchor:implement-change[]Implement Your Change
-Once you’ve been assigned to a Jira issue, you may start to implement the
required changes.
+Once you’ve been assigned to an issue, you may start to implement the required
changes.
Here are some further points to keep in mind while implementing:
- Set up a Hop development environment
- Follow the Code Style and Quality Guide of Hop
-- Take any discussions and requirements from the Jira issue or design document
into account.
+- Take any discussions and requirements from the issue or design document into
account.
- Do not mix unrelated issues into one contribution.
== anchor:open-pull-request[]Open a Pull Request
@@ -113,7 +113,7 @@ Considerations before opening a pull request:
- Make sure no unrelated or unnecessary reformatting changes are included.
- Make sure your commit history adheres to the requirements.
- Make sure your change has been rebased to the latest commits in your base
branch.
-- Make sure the pull request refers to the respective Jira, and that each Jira
issue is assigned to exactly one pull request (in case of multiple pull
requests for one Jira; resolve that situation first)
+- Make sure the pull request refers to the respective GitHub Issue, and that
each ticket is assigned to exactly one pull request (in case of multiple pull
requests for one ticket; resolve that situation first)
Considerations before or right after opening a pull request:
- Make sure that the branch is building successfully on Travis.
@@ -124,4 +124,4 @@ There is a separate guide on how to review a pull request,
including our pull re
== anchor:merge-change[merge-change]Merge Changes
-The code will be merged by a committer of Hop once the review is finished. The
Jira ticket will be closed afterwards.
+The code will be merged by a committer of Hop once the review is finished. The
ticket will be closed afterwards.
diff --git a/content/community/contribution-guides/code-review-guide.adoc
b/content/community/contribution-guides/code-review-guide.adoc
index defb5bd61..3b8d0aa98 100644
--- a/content/community/contribution-guides/code-review-guide.adoc
+++ b/content/community/contribution-guides/code-review-guide.adoc
@@ -28,7 +28,7 @@ Every review needs to check the following six aspects. *We
encourage to check th
== anchor:well-described[]Is the Contribution Well-Described
-Check whether the contribution is sufficiently well-described to support a
good review. Trivial changes and fixes do not need a long description. If the
implementation is exactly according to a prior discussion on Jira or the
development mainling list, only a short reference to that discussion is needed.
If the implementation is different from the agreed approach in the consensus
discussion, a detailed description of the implementation is required for any
further review of the contribution.
+Check whether the contribution is sufficiently well-described to support a
good review. Trivial changes and fixes do not need a long description. If the
implementation is exactly according to a prior discussion on GitHub or the
development mainling list, only a short reference to that discussion is needed.
If the implementation is different from the agreed approach in the consensus
discussion, a detailed description of the implementation is required for any
further review of the contribution.
Any pull request that changes functionality or behavior needs to describe the
big picture of these changes, so that reviews know what to look for (and don’t
have to dig through the code to hopefully understand what the change does).
@@ -36,7 +36,7 @@ Any pull request that changes functionality or behavior needs
to describe the bi
== anchor:consensus[]Is There Consensus that the Change or Feature Should Go
into Hop?
-This question can be directly answered from the linked Jira issue. For pull
requests that are created without prior consensus, a discussion in Jira to seek
consensus will be needed.
+This question can be directly answered from the linked GitHub issue. For pull
requests that are created without prior consensus, a discussion in GitHub to
seek consensus will be needed.
For [hotfix] pull requests, consensus needs to be checked in the pull request.
@@ -56,9 +56,9 @@ This question can be answered with
== anchor:follow-approach[]Does the Implementation Follow the Agreed Upon
Overall Approach/Architecture?
-In this step, we check if a contribution folllows the agreed upon approach
from the previous discussion in Jira or the mailing lists.
+In this step, we check if a contribution folllows the agreed upon approach
from the previous discussion in GitHub or the mailing lists.
-This question should be answerable from the Pull Request description (or the
linked Jira) as much as possible.
+This question should be answerable from the Pull Request description (or the
linked GitHub Issue) as much as possible.
We recommend to check this before diving into the details of commenting on
individual parts of the change.
@@ -66,7 +66,7 @@ We recommend to check this before diving into the details of
commenting on indiv
This is the detailed code review of the actual changes, covering:
-- Are the changes doing what is described in the Jira ticket or design
document?
+- Are the changes doing what is described in the ticket or design document?
- Does the code follow the right software engineering practices? Is the code
correct, robust, maintainable, testable?
- Are the changes performance aware, when changing a performance sensitive
part?
- Are the changes sufficiently covered by tests?
@@ -89,7 +89,7 @@ See more about how to
link:../documentation-contribution-guide/[contribute docum
=== anchor:en-and-ch[]Are the English and Chinese documentation updated?
-If the pull request introduces a new feature, the feature should be
documented. The Hop community is maintaining both an English and a Chinese
documentation. So both documentations should be updated. If you are not
familiar with the Chinese language, please open a Jira assigned to the
chinese-translation component for Chinese documentation translation and link it
with current Jira issue. If you are familiar with Chinese language, you are
encouraged to update both sides in one pull request.
+If the pull request introduces a new feature, the feature should be
documented. The Hop community is maintaining both an English and a Chinese
documentation. So both documentations should be updated. If you are not
familiar with the Chinese language, please open a GitHub Issue to the
chinese-translation component for Chinese documentation translation and link it
with current ticket. If you are familiar with Chinese language, you are
encouraged to update both sides in one pull request.
See more about how to contribute documentation.
diff --git
a/content/community/contribution-guides/documentation-contribution-guide.adoc
b/content/community/contribution-guides/documentation-contribution-guide.adoc
index 3a0f03217..719a50516 100644
---
a/content/community/contribution-guides/documentation-contribution-guide.adoc
+++
b/content/community/contribution-guides/documentation-contribution-guide.adoc
@@ -90,7 +90,7 @@ The API documentation is located in the docs/hop-dev-manual
subdirectory
== anchor:before-start[]Before you start start working on the documentation...
-Please make sure you have a Jira issue that corresponds to your contribution.
We require all documentation changes to refer to a Jira issue, except for
trivial fixes such as typos.
+Please make sure you have a GitHub issue that corresponds to your
contribution. We require all documentation changes to refer to a GitHub issue,
except for trivial fixes such as typos.
== anchor:multi-lang-doc[] Documentation translations
@@ -105,7 +105,7 @@ Apache Hop accepts documentation contributions through the
GitHub as Pull Reques
To prepare and submit a pull request follow these steps.
-Commit your changes to your local git repository. The commit message should
point to the corresponding Jira issue by starting with [HOP-XXXX].
+Commit your changes to your local git repository. The commit message should
point to the corresponding GitHub issue by starting with [Fix #XXXX].
Push your committed contribution to your fork of the Hop repository at GitHub.
@@ -114,4 +114,4 @@ git push origin myBranch
Go to the website of your repository fork
(`https://github.com/<your-user-name>/hop`) and use the “Create Pull Request”
button to start creating a pull request. Make sure that the base fork is hop
master and the head fork selects the branch with your changes. Give the pull
request a meaningful description and submit it.
-It is also possible to attach a patch to a Jira issue.
+It is also possible to attach a patch to a GitHub issue.
diff --git a/content/community/contribution-guides/jira-guide.adoc
b/content/community/contribution-guides/github-guide.adoc
similarity index 73%
rename from content/community/contribution-guides/jira-guide.adoc
rename to content/community/contribution-guides/github-guide.adoc
index e2b72201d..fd3870776 100644
--- a/content/community/contribution-guides/jira-guide.adoc
+++ b/content/community/contribution-guides/github-guide.adoc
@@ -1,19 +1,17 @@
---
-title: "Jira Guidelines"
+title: "GitHub Issues Guidelines"
---
-Jira is the issue tracker that is being used to track all changes and
implementation of new code or documentation in Apache Hop. This document serves
to explain the workflow that is used and what can happen after a ticket has
been created. The second purpose is to explain what you need to do to create an
complete ticket, doing so helps the developers to understand the request and
work on it.
+GitHub Issues is the issue tracker that is being used to track all changes and
implementation of new code or documentation in Apache Hop. This document serves
to explain the workflow that is used and what can happen after a ticket has
been created. The second purpose is to explain what you need to do to create an
complete ticket, doing so helps the developers to understand the request and
work on it.
[%hardbreaks]
-. <<create-ticket, Creating a Jira Ticket>>
-. <<workflow, Hop Jira Workflow>>
-. <<voting, Voting on a ticket>>
+. <<create-ticket, Creating a GitHub Issue>>
+. <<workflow, Hop GitHub Issues Workflow>>
+== anchor:create-ticket[]Creating a GitHub Issue
-== anchor:create-ticket[]Creating a Jira Ticket
-
-Writing a good Jira ticket can be a difficult task, these guidelines should
help you with writing a useful ticket that is easy to comprehend by the
developer that will handle the task.
+Writing a good ticket can be a difficult task, these guidelines should help
you with writing a useful ticket that is easy to comprehend by the developer
that will handle the task.
These criteria are only applicable when we are talking about bugs or small
changes to the code. When you have a great new idea or major change for the
product please start a discussion on our dev chat channel first, for more info
on this please take a look at our link:../code-contribution-guide/[Code
Contribution Guide].
@@ -50,16 +48,14 @@ If possible include a sample pipeline and sample data to
reproduce the situation
-== anchor:workflow[]Hop Jira Workflow
-
-The Jira workflow that is using in the development process of Apache Hop is
the following.
+== anchor:workflow[]Hop GitHub Issues Workflow
-image::/img/Jira-Workflow.png[Workflow]
+The workflow that is used in the development process of Apache Hop is the
following.
* All new issues will first get the triage status, there one of the committers
will check if all needed information is included in the ticket or if a
duplicate ticket already exists. This process can have multiple outcomes
** The ticket is complete and added to the backlog
** Additional information is requested
-** The ticket is out of scope or reporter fails to reply to questions then it
will be labeled as "won't fix"
+** The ticket is out of scope or reporter fails to reply to questions then it
will be closed with a comment
The committer will always add a comment to the ticket stating his reasoning,
why the ticket will not be handled
@@ -73,9 +69,3 @@ The committer will always add a comment to the ticket stating
his reasoning, why
* After the development is finished and you created a pull request the ticket
will be placed In Review, one of the committers will look at the code and merge
it with master if it is conforming our guidelines.
* When a ticket is done it is ready for release
-
-== anchor:voting[]Voting on a Jira Ticket
-
-====
-until following issue has been resolved voting is not possible on our jira
tickets https://jira.atlassian.com/browse/JRACLOUD-71251[JRACLOUD-71251]
-====
diff --git
a/content/community/contribution-guides/website-contribution-guide.adoc
b/content/community/contribution-guides/website-contribution-guide.adoc
index c72c6a939..e58323ee9 100644
--- a/content/community/contribution-guides/website-contribution-guide.adoc
+++ b/content/community/contribution-guides/website-contribution-guide.adoc
@@ -27,7 +27,7 @@ Next, clone your fork to your local machine.
== anchor:before-start[]Before you start start working on the documentation...
-… please make sure there exists a Jira issue that corresponds to your
contribution. We require all website changes to refer to a Jira issue, except
for trivial fixes such as typos.
+… please make sure there exists a GitHub issue that corresponds to your
contribution. We require all website changes to refer to a GitHub issue, except
for trivial fixes such as typos.
== anchor:update-or-extend[]Update or extend the documentation
@@ -53,7 +53,7 @@ Apache Hop accepts website contributions through the GitHub
as Pull Requests. Pu
To prepare and submit a pull request follow these steps.
-Commit your changes to your local git repository. The commit message should
point to the corresponding Jira issue by starting with [HOP-XXXX].
+Commit your changes to your local git repository. The commit message should
point to the corresponding GitHub issue by starting with [#XXXX].
Push your committed contribution to your fork of the Hop repository at GitHub.
@@ -61,4 +61,4 @@ git push origin myBranch
Go to the website of your repository fork
(https://github.com/<your-user-name>/hop-doc) and use the “Create Pull Request”
button to start creating a pull request. Make sure that the base fork is hop
master and the head fork selects the branch with your changes. Give the pull
request a meaningful description and submit it.
-It is also possible to attach a patch to a Jira issue.
+It is also possible to attach a patch to a GitHub issue.
diff --git a/content/community/support.adoc b/content/community/support.adoc
index 47c5a275f..88d925c77 100644
--- a/content/community/support.adoc
+++ b/content/community/support.adoc
@@ -6,7 +6,7 @@ title: Support
If you are experiencing problems using Hop then please report your problem to
our https://hop.apache.org/community/mailing-list/[mailing lists,
window="blank"]. This allows the entire community to help with your problem.
-If you found an issue or have a feature request, pleaae create a ticket in our
http://issues.apache.org/jira/browse/HOP[JIRA Issue Tracker, window="blank"].
Adding plenty of details (stack trace, logs, screenshots, ...) makes it easier
for the Hop developers to know what you exactly mean, and will allow us to
resolve your ticket faster.
+If you found an issue or have a feature request, pleaae create a ticket in our
https://github.com/apache/hop/issues[GitHub Issue Tracker, window="blank"].
Adding plenty of details (stack trace, logs, screenshots, ...) makes it easier
for the Hop developers to know what you exactly mean, and will allow us to
resolve your ticket faster.
## Alternative discussion forums and information
diff --git a/content/community/tools.adoc b/content/community/tools.adoc
index aca5d5f96..8b5d028d2 100644
--- a/content/community/tools.adoc
+++ b/content/community/tools.adoc
@@ -5,9 +5,8 @@ title: "Tools"
The following tools are used within the Hop community.
* <<github, Github>>
-* <<jira, Jira>>
+* <<Github-Issues, GitHub Issues>>
* <<jenkins, Jenkins>>
-* <<artifactory, Artifactory>>
* <<sonarcloud, Sonarcloud>>
* <<wiki, Wiki>>
* <<chat, Mattermost Chat>>
@@ -19,22 +18,17 @@ Our repositories can be found
https://github.com/apache/hop[here , window="_blan
While GitHub provides solutions to do issue tracking we use a separate
platform for this.
-== anchor:jira[]Jira
+== anchor:Github-Issues[]GitHub Issues
-All new features and issues found in Hop can be reported in our bug tracker.
If you find an issue or want to request new features first read our
link:/community/contribution-guides/jira-guide/[Jira-guide] this document
contains the basic steps needed to create a ticket that we can work on.
+All new features and issues found in Hop can be reported in our bug tracker.
If you find an issue or want to request new features first read our
link:/community/contribution-guides/github-guide/[github-guide] this document
contains the basic steps needed to create a ticket that we can work on.
-To see what we are currently working on visit our
https://issues.apache.org/jira/projects/HOP/issues[Jira Board , window="_blank"]
+To see what we are currently working on visit our
https://github.com/apache/hop/issues[GitHub Issues page , window="_blank"]
== anchor:jenkins[]Jenkins
Jenkins is a Continuous Integration/Deployment platform, when a commit has
been made and source code is changed Jenkins will automatically trigger and
test and build the code. It will also check pull requests. Our current Jenkins
setup is a fairly basic workflow which will be extended in the future to
include more checks and steps.
You can follow and see the status of all build project on our
https://ci-builds.apache.org/job/Hop/[Jenkins Website]
-== anchor:artifactory[]Artifactory
-Artifactory is a storage location for artifacts that are created by maven.
Each Jenkins build will push Artifacts to artifactory, you can then include
these artifacts in your own projects.
-
-Artifactyory can be found https://artifactory.project-hop.org[here]
-
== anchor:sonarcloud[]Sonarcloud
Sonarcloud is a platform that does code checks and validates the quality of
your code. The goal of Apache Hop is to create solid clean code, Sonarcloud
helps us achieve this goal. Currently it does not look good yet but we are
still in a stage where we are refactoring and cleaning up the Hop code base.
diff --git a/layouts/partials/footer.html b/layouts/partials/footer.html
index 22deabe9b..fc72f780e 100644
--- a/layouts/partials/footer.html
+++ b/layouts/partials/footer.html
@@ -13,7 +13,7 @@
</dl>
<dl>
<dt>Community</dt>
- <dd><a target="_blank"
href="https://issues.apache.org/jira/projects/HOP/issues";>Jira</a></dd>
+ <dd><a target="_blank"
href="https://github.com/apache/hop/issues";>GitHub Issues</a></dd>
<dd><a target="_blank"
href="https://chat.project-hop.org";>Chat</a></dd>
<dd><a href="/community/team/">Team</a></dd>
</dl>
diff --git a/static/doap_Hop.rdf b/static/doap_Hop.rdf
index a0c0b2e02..95aa3435e 100644
--- a/static/doap_Hop.rdf
+++ b/static/doap_Hop.rdf
@@ -35,16 +35,16 @@ Hop is an entirely new open source data integration
platform that is easy to use
Hop aims to be the future of data integration. Visual development enables
developers to be more productive than they can be through code. Our Design
once, run anywhere workflows and pipelines can be designed in the Hop Gui and
run on the Hop native engine (local or remote), or on Spark, Flink, Google
Dataflow or AWS EMR through Beam. Lifecycle Management enables developers and
administrators to switch between projects, environments and purposes without
leaving your train of thought.
</description>
- <bug-database rdf:resource="https://issues.apache.org/jira/projects/HOP/";
/>
+ <bug-database rdf:resource="https://github.com/apache/hop/issues"; />
<mailing-list rdf:resource="http://hop.apache.org/community/mailing-list/";
/>
<download-page rdf:resource="http://hop.apache.org/download/"; />
<programming-language>Java</programming-language>
<category rdf:resource="https://projects.apache.org/category/big-data"; />
<release>
<Version>
- <name>Apache Hop 0.70</name>
- <created>2021-04-08</created>
- <revision>0.70</revision>
+ <name>Apache Hop 2.2.0</name>
+ <created>2022-12-08</created>
+ <revision>2.2.0</revision>
</Version>
</release>
<repository>
