Skip to content
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 release / tag? #58

Open
floatingstatic opened this issue Jan 19, 2024 · 3 comments
Open

New release / tag? #58

floatingstatic opened this issue Jan 19, 2024 · 3 comments

Comments

@floatingstatic
Copy link

The last release of RANCID was back in 2020 (3.13). There have been a number of changes since then that have landed here. Are there plans to do a release anytime soon? For my own use case I can use the master branch or a commit sha here but it is often more convenient to pull down a tagged release from git or the shrubbery ftp servers.

Thanks in advance!

@bylienator
Copy link

Would like to up this question as well.

I guess it's a good thing that commits are still happening but over time the current release will become less compatible with newer devices/software. We're currently also using version 3.13 without any issues, albeit with a couple of custom patches from master, but are wondering if the release model has changed and it's now recommended to directly use master instead of waiting on a new release?

This might also be important information for certain distros that only update the package on a new release/version.

@jk2lx
Copy link

jk2lx commented Mar 5, 2024

I want to second the previous comments and would appreciate a new release. A variety of features/fixes have been added over the last 4 years but without a new tagged release, they won't be able via the distros which still offer Rancid.

@jrbinks
Copy link

jrbinks commented Jun 20, 2024

@haussli will need to say for sure, but I've a feeling that this github repo was an 'occasional' reflection of a private reop where the work actually happens, rather than the 'active' for-real actual repo of development (perhaps it doesn't matter in the end).

Regardless, yes cutting another release would be a good thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants