-
Notifications
You must be signed in to change notification settings - Fork 907
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
New releases scheduling #2520
Comments
Thank for opening this discussion, lets focus to prepare some priority list/enhancements, based on that we can bucket them in to future releases.Hope this make sense. |
Pinging @utoni, @0xA50C1A1, @aouinizied, @vel21ripn, @dsokoloski, @koltiradw |
My apologies for not seeing this sooner! I love the idea of a more structured (eg: 4 month cycle), and rapid release schedule. The project activity, number of commits, new features, bug fixes, dissectors, etc. is IMHO high enough to support a faster release schedule. Thumbs up from Team Netify! ...and if we can collaborate in anyway, please let me know. |
@IvanNardi and all Participants Can we create the agenda/wish list we can address with next roadmap.From my side I'm adding following. |
This discussion is more about the (new) scheduling of the new releases. I renamed this issue to make it clearer |
Thanks for the advice, Will update the Roadmap discussion. |
In general I would appreciate having more frequent nDPI releases. But from my perspective it would be great if that wishlist could be somehow integrated into GitHub for transparency. I think of having a project/milestone(s), so everyone knows what the next release release includes. That'll also help me upgrading nDPId. |
Closing. Let's continue on #2645 |
nDPI releases have always been cut approximately every 6-9 months.
As reported by @lucaderi (https://www.ntop.org/ndpi/released-ndpi-4-10-421-protocols-55-flow-risks-several-improvements-getting-ready-for-fpc/) there were some discussions recently to change that and provide a new release more frequently with some kind of hard scheduling (i.e. a new release every X months), similar to what other projects (linux kernel, ubuntu, DPDK, ...) are doing.
The idea is to make a new release every 4 months with a roadmap like: 01/12/2024, 01/04/2025,...
That is a tradeoff between providing frequent updates and the cost of cutting a release.
Any thoughts/suggestions?
The text was updated successfully, but these errors were encountered: