You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@karaf.apache.org by jb...@apache.org on 2025/09/25 12:50:03 UTC
svn commit: r1928761 - karaf/site/production
Author: jbonofre
Date: Thu Sep 25 12:50:03 2025
New Revision: 1928761
Log:
[scm-publish] Updating main website contents
Modified:
karaf/site/production/community.html
karaf/site/production/feed.xml
Modified: karaf/site/production/community.html
==============================================================================
--- karaf/site/production/community.html Thu Sep 25 12:45:02 2025 (r1928760)
+++ karaf/site/production/community.html Thu Sep 25 12:50:03 2025 (r1928761)
@@ -151,24 +151,19 @@
<div class="card-body d-flex flex-column align-items-start">
<strong class="d-inline-block mb-2 text-primary">Bug Tracker, IRC, and CI</strong>
<h4 class="mb-0">
- <a class="text-dark">Jira</a>
+ <a class="text-dark">GitHub Issues</a>
</h4>
- <p class="card-text"> [ <a href="https://issues.apache.org/jira/browse/KARAF" target="_blank">visit</a> ]</p>
+ <p class="card-text"> [ <a href="https://github.com/apache/karaf/issues" target="_blank">karaf</a> ] [ <a href="https://github.com/apache/karaf-decanter/issues" target="_blank">decanter</a> ] </p>
<h4 class="mb-0">
- <a class="text-dark">Jenkins</a>
+ <a class="text-dark">GitHub Actions</a>
</h4>
- <p class="card-text"> [ <a href="https://builds.apache.org/view/H-L/view/Karaf/" target="_blank">visit</a> ]</p>
-
- <h4 class="mb-0">
- <a class="text-dark">#apache-karaf on Freenode</a>
- </h4>
- <p class="card-text"> [ <a href="irc://irc.freenode.net/apache-karaf" target="_blank">visit</a> ]</p>
+ <p class="card-text"> [ <a href="https://github.com/apache/karaf/actions" target="_blank">karaf</a> ] [ <a href="https://github.com/apache/karaf-decanter/actions" target="_blank">decanter</a> ] </p>
<h4 class="mb-0">
<a class="text-dark">#karaf on the-asf.slack.com</a>
</h4>
- <p class="card-text"> [ <a href="https://the-asf.slack.com" target="_blank">visit</a> ]</p>
+ <p class="card-text"> [ <a href="https://the-asf.slack.com" target="_blank">The ASF Slack</a> ]</p>
</div>
</div>
</div>
@@ -202,7 +197,7 @@
<div class="row mb-5 mt-5">
<div class="col">
<h4 class="pb-3 mb-4">Report bugs and feature requests</h4>
- <p>Did you find a bug or want something implemented? Please report an issue in our <a href="https://issues.apache.org/jira/browse/KARAF">issue tracker</a>. When creating a bug make sure you document the steps to reproduce the issue and provide all necessary information like OS, versions your use, logs. When creating a feature request document your requirements first. Try to not directly describe the solution.</p>
+ <p>Did you find a bug or want something implemented? Please report an issue in our <a href="https://github.com/apache/karaf/issues">Karaf issue tracker</a> (or the issue tracker for the subproject like <a href="https://github.com/apache/karaf-decanter/issues">Karaf Decanter issue tracker</a>). When creating a bug make sure you document the steps to reproduce the issue and provide all necessary information like OS, versions your use, logs. When creating a feature request document your requirements first. Try to not directly describe the solution.</p>
<p>If you want to dive into development yourself then you can also browse for open issues or features that need to be implemented. Take ownership of an issue and try fix it. Before doing a bigger change describe the concept/design of what you plan to do. If unsure if the design is good or will be accepted discuss it on the dev list.</p>
</div>
@@ -213,8 +208,8 @@
<h4 class="pb-3 mb-4">Provide changes in a Pull Request</h4>
<p>The best way to provide changes is to fork karaf repo on github and provide a pull request with your changes. To make it easy to apply your changes please use the following conventions :</p>
<ul class="community">
- <li>Every pull request should have a matching jira issue.</li>
- <li>Do the change in a branch that is named like the jira issue id e.g KARAF-1234.<br/>To create this branch you can use:<br/>
+ <li>Every pull request should have a matching GitHub issue.</li>
+ <li>Do the change in a branch.<br/>To create this branch you can use:<br/>
<code>git clone http://github.com/apache/karaf</code><br/>
<code>git fetch --all</code><br/>
<code>git checkout -b my-branch origin/main</code><br/>
@@ -223,7 +218,6 @@
<code>git push GitHubUser my-branch --force</code>
</li>
<li>PRs should be based on main. We are taking care of cherry picking the PR commits on target branches if needed.</li>
- <li>Every commit in the branch should start with the jira issue id like this "[KARAF-123] More details"</li>
<li>If you have a group of commits related to the same change, please squash your commits into one and force push your branch using <code>git rebase -i apache/main</code></li>
<li>Test that your change works by adapting or adding tests.</li>
<li><a href="http://programmer.97things.oreilly.com/wiki/index.php/The_Boy_Scout_Rule">Follow the boy scout rule to "Always leave the campground cleaner than you found it."</a></li>
@@ -246,7 +240,7 @@
If you want to review a PR and if you are a committer, use the "Reviewer" entry on the right menu on GitHub.<br/>
When reviewing check if the changes are done in a clean way and are tested with a unit and possibly integration test. Check that the build does not report more test failures than before. If you are not a committer then write a comment if you recommend a merge or not. Provide good instructions for the contributor how to improve his PR if it is not yet ok. Make sure you do a review timely. By commenting that you do a review you kind of block others from applying the change.</p>
<p class="alert alert-primary" role="alert">
- NB: Jenkins performs a build for each pull request. You can trigger a new build on a pull request using "retest this please" in a PR comment.
+ NB: CI performs a build for each pull request. You can trigger a new build in GitHub or by pushing a new empty commit.
</p>
</div>
</div>
@@ -284,7 +278,7 @@
Use the merge button on github (for committer).
</li>
<li>Eventually backport commits to bugfix branches using <code>git cherry-pick</code></li>
- <li>Make sure you document the fix in jira by adding the fix versions and resolve the jira issue.</li>
+ <li>Make sure you document the fix in the GitHub Issue by adding the target milestone and resolve the issue.</li>
<li>You can delete the PR branch : <br>
<code>> git branch -D pr-xxx</code>.</li>
</ul>
@@ -306,7 +300,7 @@
<div class="row mb-5 mt-5">
<div class="col">
<h2 class="pb-3 mb-4 font-italic border-bottom"><i class="fas fa-shipping-fast"></i> Support</h2>
- <p>If you are experiencing problems using Karaf then please report your problem to our <a href="https://issues.apache.org/jira/browse/KARAF">issue tracker</a>.
+ <p>If you are experiencing problems using Karaf then please report your problem to our <a href="https://github.com/apache/karaf/issues">issue tracker</a>.
You may also find it useful to discuss your issues with the community on the mailing lists or IRC.</p>
</div>
</div>
@@ -338,7 +332,7 @@
<ul class="community">
<li>provide us with a JUnit test case that demonstrates your issue. e.g. if you think you've found a bug, can you create a test case to demonstrate the bug ?</li>
<li>submit a patch fixing the bug! (we also buy you beer when we meet you if you submit bug fixes :) )</li>
- <li>for memory leak or performance related issues, if you can run a profiler on your test case and attach the output as a file (or zipped file if it's huge) to the JIRA we can normally fix things much quickly. E.g. you could run jmap/jhat, JProfiler or YourKit on your code and send us the output. To find memory leaks it's quicker to resolve if you can tell us what classes are taking up all of the RAM; we can normally figure out what's wrong from that</li>
+ <li>for memory leak or performance related issues, if you can run a profiler on your test case and attach the output as a file (or zipped file if it's huge) to the GitHub Issue we can normally fix things much quickly. E.g. you could run jmap/jhat, JProfiler or YourKit on your code and send us the output. To find memory leaks it's quicker to resolve if you can tell us what classes are taking up all of the RAM; we can normally figure out what's wrong from that</li>
</ul>
</div>
</div>
Modified: karaf/site/production/feed.xml
==============================================================================
--- karaf/site/production/feed.xml Thu Sep 25 12:45:02 2025 (r1928760)
+++ karaf/site/production/feed.xml Thu Sep 25 12:50:03 2025 (r1928761)
@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.0.1">Jekyll</generator><link href="https://karaf.apache.org/feed.xml" rel="self" type="application/atom+xml" /><link href="https://karaf.apache.org/" rel="alternate" type="text/html" /><updated>2025-09-16T19:05:33+02:00</updated><id>https://karaf.apache.org/feed.xml</id><title type="html">Apache Karaf - The modulith runtime</title><subtitle>Karaf provides modulith runtime for the enterprise, running on premise or on cloud. Focus on your business code and applications, Apache Karaf deals with the rest.</subtitle></feed>
\ No newline at end of file
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.0.1">Jekyll</generator><link href="https://karaf.apache.org/feed.xml" rel="self" type="application/atom+xml" /><link href="https://karaf.apache.org/" rel="alternate" type="text/html" /><updated>2025-09-25T07:47:26-05:00</updated><id>https://karaf.apache.org/feed.xml</id><title type="html">Apache Karaf - The modulith runtime</title><subtitle>Karaf provides modulith runtime for the enterprise, running on premise or on cloud. Focus on your business code and applications, Apache Karaf deals with the rest.</subtitle></feed>
\ No newline at end of file