Comments (9)
More todo tasks: hickory-dns/docker#2
from hickory-dns.
/cc @siretart for https://packages.debian.org/search?searchon=sourcenames&keywords=trust-dns
from hickory-dns.
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?).
from hickory-dns.
It also seems confusing if Hickory 0.25 is effectively the same code as trust-dns 0.24 (is that what you're planning?).
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.
I'd want the rename notice in the READMEs to look different for old vs new name crates.
Yes, I was planning to update the notices for the back references on the first publish of Hickory crates.
from hickory-dns.
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.
from hickory-dns.
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.
from hickory-dns.
I'm planning to do this later today. That is,
- Existing
trust-dns
crates will be published as0.23.1
- I will then move and rename the
trust-dns
repo to https://github.com/hickory-dns/hickory-dns - Then I will publish the first release of Hickory DNS as
0.24.0
For reference, the new crates will be:
trust-dns crate | hickory crate |
---|---|
trust-dns-proto | hickory-proto |
trust-dns-resolver | hickory-resolver |
trust-dns-recursor | hickory-recursor |
trust-dns-client | hickory-client |
trust-dns-util | hickory-util |
trust-dns | hickory-dns |
from hickory-dns.
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.
from hickory-dns.
One task left, I still need to update the sites for Hickory DNS domains.
from hickory-dns.
Related Issues (20)
- Low level send method in resolver HOT 8
- Additional error context HOT 4
- impl RecordData for RData HOT 1
- Update rustls to latest version HOT 2
- Add the ability to bind/unbind ports dynamically
- Introduce TlsConnect and QuicConnect trait to be more flexible HOT 4
- Resolver couldn't handle response that have lots of records HOT 13
- tokio::JoinSet and hickory_resolver::Resolver causes "Cannot start a runtime from within a runtime" HOT 2
- Forwarder seems to not use /etc/hosts despite `use_hosts_file == true` HOT 3
- Presence of a faulty nameserver in system config causes client side lookups to take forever HOT 1
- Reverse lookup fails when there are multiple PTR records HOT 1
- www.hickory-dns.org does not work - 404 HOT 5
- SIG(0) RFC2931 is not listed as supported HOT 1
- Missing point of contact for security issues HOT 3
- `IN` keyword is not accepted HOT 2
- Request for a wildcard with ANY returns nothing HOT 2
- Handle sockets that have been shut down HOT 5
- Make ```hickory_proto::quic::QuicClientStream``` clonable
- why hickory-proto 0.24.1 ring dependencies is still 0.16.20 HOT 4
- Not convenient to call bind_with_addr to make a AsyncResolver HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from hickory-dns.