SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-06-11 01:41:55 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Stable versioning #2067

New Issue
Open
opened 2025-11-20 06:12:10 -05:00 by saavagebueno · 6 comments
saavagebueno commented 2025-11-20 06:12:10 -05:00
Owner
Copy Link

Originally created by @Lamera on GitHub (Jul 15, 2025).

Describe the problem

I would like to provide feedback regarding the update frequency of Netbird.

Currently, updates are released very frequently. I very much appreciate that.
But sometimes this leads to interruptions and additional workload. I suggest adjusting the release schedule to monthly intervals, which would allow for better planning and implementation.
Benefits:

  • Increased efficiency in deployment and troubleshooting.
  • Reduced interruptions to ongoing operations.
  • Consolidated and comprehensive feature enhancements instead of frequent small changes.
Originally created by @Lamera on GitHub (Jul 15, 2025). **Describe the problem** I would like to provide feedback regarding the update frequency of Netbird. Currently, updates are released very frequently. I very much appreciate that. But sometimes this leads to interruptions and additional workload. I suggest adjusting the release schedule to monthly intervals, which would allow for better planning and implementation. Benefits: - Increased efficiency in deployment and troubleshooting. - Reduced interruptions to ongoing operations. - Consolidated and comprehensive feature enhancements instead of frequent small changes.
saavagebueno added the feature-request label 2025-11-20 06:12:10 -05:00
saavagebueno commented 2025-11-20 06:12:12 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Jul 15, 2025):

This will become a lot more stable once we reach the 1.0 milestone. We are still very much in a development mode while trying to balance it with stabilization efforts: implementing the remaining essential features, fixing discovered edge cases and redesigning existing (usually older) subsystems for long-term maintainability.

@nazarewk commented on GitHub (Jul 15, 2025): This will become a lot more stable once we reach the `1.0` milestone. We are still very much in a development mode while trying to balance it with stabilization efforts: implementing the remaining _essential_ features, fixing discovered edge cases and redesigning existing (usually older) subsystems for long-term maintainability.
saavagebueno commented 2025-11-20 06:12:12 -05:00
Author
Owner
Copy Link

@san983 commented on GitHub (Jul 15, 2025):

This will become a lot more stable once we reach the 1.0 milestone. We are still in heavy development mode: redesigning a lot of existing and introducing many new features.

May I ask if there is a roadmap for that? Thanks!

@san983 commented on GitHub (Jul 15, 2025): > This will become a lot more stable once we reach the `1.0` milestone. We are still in heavy development mode: redesigning a lot of existing and introducing many new features. May I ask if there is a roadmap for that? Thanks!
saavagebueno commented 2025-11-20 06:12:12 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Jul 15, 2025):

We're aiming for late 2025/early 2026 for the first stable release.

@nazarewk commented on GitHub (Jul 15, 2025): We're aiming for late 2025/early 2026 for the first stable release.
saavagebueno commented 2025-11-20 06:12:12 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jul 15, 2025):

Hello @san983 to add to @nazarewk message. We are moving towards 1.0 and the way think about is more related a few core features that will come which may change our management to client protocol, e.g. IPv6 support and incremental Network maps.

We are looking at starting the development of these changes this quarter, and with tests and rollout, we should have a 1.0 version late 2025 as mentioned.

With that said, our pace of development and releases is related to improvements and smaller features, but we have tens of thousands of organizations relying on NetBird for their remote access and production environments.

On the other hand, we are also developing an auto-update feature that will allow you to pin a specific version for your clients.

@mlsmaycon commented on GitHub (Jul 15, 2025): Hello @san983 to add to @nazarewk message. We are moving towards 1.0 and the way think about is more related a few core features that will come which may change our management to client protocol, e.g. IPv6 support and incremental Network maps. We are looking at starting the development of these changes this quarter, and with tests and rollout, we should have a 1.0 version late 2025 as mentioned. With that said, our pace of development and releases is related to improvements and smaller features, but we have tens of thousands of organizations relying on NetBird for their remote access and production environments. On the other hand, we are also developing an auto-update feature that will allow you to pin a specific version for your clients.
saavagebueno commented 2025-11-20 06:12:12 -05:00
Author
Owner
Copy Link

@san983 commented on GitHub (Jul 15, 2025):

Hello @san983 to add to @nazarewk message. We are moving towards 1.0 and the way think about is more related a few core features that will come which may change our management to client protocol, e.g. IPv6 support and incremental Network maps.

We are looking at starting the development of these changes this quarter, and with tests and rollout, we should have a 1.0 version late 2025 as mentioned.

With that said, our pace of development and releases is related to improvements and smaller features, but we have tens of thousands of organizations relying on NetBird for their remote access and production environments.

On the other hand, we are also developing an auto-update feature that will allow you to pin a specific version for your clients.

Thanks for the detailed panorama and roadmap @nazarewk and @mlsmaycon.

As installing a new version of Netbird causes the service to restart, which currently destroys and rebuilds the tunnels, is there currently a way of doing a disconnect-less upgrade? Actually moved my question to a new ticket => https://github.com/netbirdio/netbird/issues/4159

@san983 commented on GitHub (Jul 15, 2025): > Hello [@san983](https://github.com/san983) to add to [@nazarewk](https://github.com/nazarewk) message. We are moving towards 1.0 and the way think about is more related a few core features that will come which may change our management to client protocol, e.g. IPv6 support and incremental Network maps. > > We are looking at starting the development of these changes this quarter, and with tests and rollout, we should have a 1.0 version late 2025 as mentioned. > > With that said, our pace of development and releases is related to improvements and smaller features, but we have tens of thousands of organizations relying on NetBird for their remote access and production environments. > > On the other hand, we are also developing an auto-update feature that will allow you to pin a specific version for your clients. Thanks for the detailed panorama and roadmap @nazarewk and @mlsmaycon. ~As installing a new version of Netbird causes the service to restart, which currently destroys and rebuilds the tunnels, is there currently a way of doing a disconnect-less upgrade?~ Actually moved my question to a new ticket => https://github.com/netbirdio/netbird/issues/4159
saavagebueno commented 2025-11-20 06:12:12 -05:00
Author
Owner
Copy Link

@Wouter0100 commented on GitHub (Sep 29, 2025):

I'm very curious to the state of this roadmap. Is 1.0 still planned late 2025 / early 2026?

Thanks!

@Wouter0100 commented on GitHub (Sep 29, 2025): I'm very curious to the state of this roadmap. Is 1.0 still planned late 2025 / early 2026? Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label feature-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2067
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?