New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Renamed Hudson to Jenkins in UI #6797
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good so far - thanks for working on this.
regarding paperwork:
the commit should have your full name next to the email address, you can check it by looking at the patch: https://github.com/apache/netbeans/pull/6797.patch where you see only your nickname, feel free to force push into this PR after fixing it locally. This wiki page has some instructions in the bootstrap section.
ide/hudson.ui/src/org/netbeans/modules/hudson/ui/wizard/InstanceDialog.java
Outdated
Show resolved
Hide resolved
php/hudson.php/src/org/netbeans/modules/hudson/php/options/HudsonOptions.java
Outdated
Show resolved
Hide resolved
php/hudson.php/src/org/netbeans/modules/hudson/php/ui/options/HudsonOptionsPanelController.java
Outdated
Show resolved
Hide resolved
ide/hudson/src/org/netbeans/modules/hudson/impl/HudsonJobBuildImpl.java
Outdated
Show resolved
Hide resolved
The artwork needs to be changed as well. Hudson and Jenkins have different mascot. |
I have pushed changes after making changes as told, was that the right thing to do? I am asking this as I am new to the community |
thats fine during review, but before merge it would be good if you would squash everything locally to one commit, make sure the commit message is how you like it and then force push into the PR. This PR would have to do that anyway, due to the commit author field, see #6797 (review) |
Hi @mbien, I've gone through the contributing guidelines for the NetBeans project and I'm seeking some clarification on the squashing process. I attempted to squash my commits interactively in Vim, but encountered conflicts during the process. Specifically, I'm puzzled by an unexpected commit in the pull request 6797. In commit 8916655, I reconfigured the author's name. Subsequently, when I executed Could you please provide further guidance on the squashing process and help me understand why the mentioned merge commit was automatically generated? I want to ensure that I follow the correct procedures and address any issues promptly. Your expertise in clarifying this matter would be greatly appreciated. |
I assume you fixed the global git config already, you can check with here is how I would do it: lets put your commits on top of latest master (this changes the history in your branch, but we have to do this anyway): check out your branch locally (you likely already have that)
check with:
so you see that your 2 commits are indeed on top of all other commits. now lets squash the 2 commits:
this will open an editor with instructions. For this use case here, you have to change "pick" into "s" on all commits except the commit in the first line (so only the second line basically). This will squash the second commit into the first and then ask you to update the commit message, which you should do. lets check again:
worked! Now lets fix the commit header, since it would still have the wrong name:
check with now to push, you have to add the
and the changes should land here |
473b157
to
6417f92
Compare
@rothardo you don't have to push merge commits right away, its ok if the branch is a little bit out of date. |
ide/hudson.ui/src/org/netbeans/modules/hudson/ui/resources/instance.png
Outdated
Show resolved
Hide resolved
Well, let's keep the number of commits minimal for a PR. Unless there is no conflict, or a dependency, you do not need to merge anything back from the master branch. In those rare cases when needed, it's better to do a rebase instead of adding a merge commit. Since you are working on your own branch, it is Ok to amend a previous commit. This way most PR-s would be only 1 commit. That way you simply skip the squashing. |
ea29697
to
e4b3098
Compare
Hello, @mbien Could you please confirm if this issue still requires changes? If not, could you kindly guide me through the procedure for making this more merge ready? Thank you. |
@rothardo we have to figure out how to handle property file keys, since this PR here does currently rename a few but not all which makes it inconsistent. But I leave this to other reviewers to decide, esp those who wanted to make this change only in UI instead of a full rename. edit: CI for this PR does also create a dev-build zip (e.g: https://github.com/apache/netbeans/actions/runs/7164936342?pr=6797) which can be used for manual testing. I haven't checked it yet, maybe there are more icons to change but I hope not ;) |
I already stated, that I think we should only follow the name change on the surface. And it seems this PR is mostly in line with that. IMHO we gain little renaming packages or other things. We risk though internal breakage as we have sites that refer to modules, options, translations by name and these are hard to catch. Going through this PR @rothardo I notice:
All in this looks sane to me. |
Hi @matthiasblaesing , I wanted to provide you with an update on the PR. I have addressed the concerns raised during the review process, and I've reverted the keys that were changed, and most modifications are limited to UI string updates, aligning with the consensus that we should primarily follow the name change on the surface to minimize internal breakage. I've initiated discussions on the Jenkins community forum regarding the licensing of the logo. The press page on Jenkins provides some information, but it's not conclusive. I believe obtaining clarity on this is crucial. If you have any additional insights or thoughts on these matters, please do share them with me. Thank you for your ongoing support. |
f6bb5a7
to
840b0fd
Compare
Hi @mbien and @matthiasblaesing , I wanted to update you on the licensing clarification I received regarding the Jenkins artwork used in the Apache NetBeans contribution. Mark Waite, a member of the Jenkins Governance Board, provided insights into the licensing terms, which are detailed on the Jenkins Artwork page. I've received clarity on the licensing terms for the Jenkins artwork used in the Apache NetBeans contribution. According to the Creative Commons Attribution-ShareAlike 3.0 Unported License, the artwork, i.e instance.png is redistributable with specific conditions. The licensing details are as follows:License: Creative Commons Attribution-ShareAlike 3.0 Unported License Now I would like to seek your guidance in incorporating the recently obtained license information for the Jenkins artwork into the ide/hudson.ui/licenseinfo.xml file. Can you specify the appropriate structure or format for including this licensing information in the XML file? |
@rothardo thanks for staying with this. My proposal how to handle the logo would be: That is in https://github.com/matthiasblaesing/netbeans (branch: pr-6797) feel free to squash into your changes, if it makes sense to you. |
7a8d60c
to
dba9d02
Compare
1f1e5bc
to
bfd0a28
Compare
@mbien and @matthiasblaesing I have force Pushed with the update in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To me this looks sane.
@rothardo thank you for the update
@junichi11 @lkishalmi @mbien what do you think? Do you have objections to merging this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've left comments about the URLs.
Other than that, it looks good to me.
Thank you for your work!
@mbien should I change the URLs too as per @junichi11 's comment? |
@rothardo yes, please do so. change |
589dfe0
to
3b694ec
Compare
@mbien I have completed the necessary changes as adviced |
thanks, I looked through the comments and diff and it looks like all were resolved. Going to merge once CI is green. @rothardo congrats to your first contribution |
Thank you, @mbien @matthiasblaesing @junichi11 @ebarboni @lkishalmi |
@rothardo Congrats! |
Description
In the UI, Hudson was seamlessly renamed as Jenkins without altering any directory, cluster, package, or method names.
Why was it required?
Hudson is no more but NetBeans is still using it in the UI:
FIxes the Issue
Rename Hudson to Jenkins #6628
Modifications made to
After Changes in the UI it looks like this:
And as stated above Hudson renamed as Jenkins without altering any hudson directory, cluster, package, or method names:
By opening a pull request you confirm that, unless explicitly stated otherwise, the changes -
Yes
Yes