mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[GH-ISSUE #2051] Hickory DNS rebranding #864
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#864
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bluejekyll on GitHub (Oct 6, 2023).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2051
Trust-DNS is going to be rebranded to Hickory DNS and the repo moved into the https://github.com/HickoryDNS organization. This isn't something I think we should do overnight, so I'm going to list out the steps to get there, imo, if folks have other opinions about what is needed here, please let me know. For more background on this rebranding, please read this blog post: https://bluejekyll.github.io/blog/posts/announcing-hickory-dns/
Before moving the repo:
Before move, not part of the 0.23.1 release of Trust-DNS
After moving the repo:
Contributors
upsteamgit remotes to the new repo@djc commented on GitHub (Oct 9, 2023):
I think we should move the repo basically now. Because GitHub leaves a redirect in place (both for Git protocols and at the HTTP level), this has basically no downside. I would probably either publish 0.24 under both names or publish a 0.23.1 with rename notices in the README and publish 0.24.0 only under the new name -- I'd want the rename notice in the READMEs to look different for old vs new name crates. It also seems confusing if Hickory 0.25 is effectively the same code as trust-dns 0.24 (is that what you're planning?).
@bluejekyll commented on GitHub (Oct 9, 2023):
yes, that was effectively my plan. I thought it might give people a simpler cut-over point. That is, there are potentially breaking changes in 0.24, and so they can upgrade without the name changes, that might have some of their own confusion. I also thought we could use 0.25 in Hickory to go through and remove deprecated interfaces.
Yes, I was planning to update the notices for the back references on the first publish of Hickory crates.
@bluejekyll commented on GitHub (Oct 9, 2023):
I think you're correct about the moving of the repo, I think I can take care of that today. Though my preference is to publish 0.24 just in case there are some delays due to a move (keys, etc) that could stop that from going through.
@bluejekyll commented on GitHub (Oct 9, 2023):
FYI, @djc and I discussed in more detail. We decided that given the name changes themselves are breaking changes, it doesn't make sense to deploy 0.24 to trust-dns names. Instead, 0.24 will be deployed to Hickory DNS names. There will be a final 0.23.1 release to the trust-dns names that is just a notice of the branding changes.
@bluejekyll commented on GitHub (Oct 13, 2023):
I'm planning to do this later today. That is,
trust-dnscrates will be published as0.23.1trust-dnsrepo to https://github.com/hickory-dns/hickory-dns0.24.0For reference, the new crates will be:
@williamdes commented on GitHub (Oct 13, 2023):
More todo tasks: https://github.com/trust-dns/docker/issues/2
@williamdes commented on GitHub (Oct 13, 2023):
/cc @siretart for https://packages.debian.org/search?searchon=sourcenames&keywords=trust-dns
@bluejekyll commented on GitHub (Oct 25, 2023):
FYI: #2069, we're posting unmaintained notices for the non-feature change updates after 0.23.1 and 0.23.2. This should give folks notices that the project has been rebranded after 0.23 without breaking builds until the they update dependencies.
@bluejekyll commented on GitHub (Oct 25, 2023):
One task left, I still need to update the sites for Hickory DNS domains.