Rename packages organization from com.velocidi to com.kevel
#745
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I'd rather not move from one old name ( |
jcazevedo
requested changes
Oct 14, 2024
| @@ -21,7 +21,7 @@ | |||
| * 02110-1301 USA, or see the FSF site: http://www.fsf.org. | |||
| */ | |||
|
|
|||
| package com.velocidi.apso.hashing; | |||
| package com.kevel.apso.hashing; | |||
There was a problem hiding this comment.
Can we rollback the other changes in this file? I suspect some unwanted IDE shenanigans went unnoticed here.
Yeah, totally missed that 😅 Done! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes the packages from the
com.velociditocom.kevelorganization to reflect the organizational change. For now, it doesn't touch the publishing organization as I still need to figure out some things for that.After making the change I wondered if we'd want to use
adzerkinstead to be consistent with the GitHub organization name, what do you think?I am leaving this with the
do not merge labelfor now, as I know we'd like to get a Pekko update without this impacting its release. I will also try to figure out the publish organization to try to get it all at once.Does this change relate to existing issues or pull requests?
No.
Does this change require an update to the documentation?
Updated the
READMEdocs as well.How has this been tested?
Relying on CI to validate everything keeps working.