-
Notifications
You must be signed in to change notification settings - Fork 232
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 version? #350
Comments
@kloczek: I think that it will be nice to have a perfect @EasyNetDev PR before it :/ |
I think last PRs before the new build will be: |
@paulusmack: About the Debian 12 freeze deadline: cc: @bootc. |
I think we're very close to being able to do a release; it's mostly now a matter of writing some release notes to go into the README file and then creating the tarballs and putting them up. I'd like to hear from the contributors to this release if there are any particular items that should be mentioned in the README. @carlsonj could you check that all appears to be OK on Solaris please? |
@thesamesam how does current PPP/master compile on Gentoo with the latest GCC (as you found with sstp-client)? |
Cheers for the ping! Let me have a look either tomorrow or day after. |
@thesamesam is there anything else you'd like to test specifically? I've run pppoe-server with this as well on my test host, and I'm fairly certain if there are problems I'll be able (and more than willing to ... time permitting which since you're pinging me on other bugs know is fairly limited).
|
@jkroonza The main task is to just port the ebuild to autotools and see if everything works okay, or if we're missing some way to do something we used to do in the new setup. Ideally someone who uses ppp could do that (you? 😀) at least for a first pass, then I could tidy it up if needed. |
I can build it standalone from master branch, so if a release is made I'm sure I'll be able to port the ebuild, hopefully including most patches that wasn't merged upstream (and with permission from original authors ideally submit them here too). If any individual patch gets stuck we should probably also evaluate if it's a required patch, ie, reach out or block it temporarily with a news item. That's Gentoo problems though, not ppp, and IMHO shouldn't be a cause for blocking a new release. If we need assistance from ppp I'm sure we will be able to motivate a 2.5.1 release. |
I think the tree is ready for release. Last call for anything that really needs to be fixed before 2.5.0... |
2.5.0 is out there now. |
Dear all, @paulusmack will prepare a 2.5.1 release build and ask some questions: Can you look it? Thanks in advance. |
PPP 2.5.1 has been released (2024-09-18) |
Dear all, @paulusmack has planned a new build in few days, you have not patches? @bootc, @rfc1036: What is the latest date to have a new PPP version (2.5.2) in Debian Testing before Debian 13 freeze? |
Are any patches required? |
Highly doubt it. No functional changes, mostly relatively minor fixes, and one change to actually expose functionality rp-pppoe already implements to the ppp user scripts. |
PPP 2.5.2 has been released (2024-12-31) |
ppp-2.4.9...master shows already +130 commits.
It is always better to make release with smaller batches of commits.
Please consider to make the new release soon.
The text was updated successfully, but these errors were encountered: