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

Version for a new install? 1.7.x? 1.8? 2.0?!? Latest stable? #1661

Closed
eparadis opened this issue Dec 14, 2024 · 2 comments
Closed

Version for a new install? 1.7.x? 1.8? 2.0?!? Latest stable? #1661

eparadis opened this issue Dec 14, 2024 · 2 comments

Comments

@eparadis
Copy link

I'm looking to set up a new installation of providence and pawtucket2.

The front page says "1.7"

The latest News post is from two years ago and says "1.7.16 is released!"

The github project README says "1.7.17" is the newest release.

An issue from over a year ago is talking about people using "1.8" in production.

One of the most recent issues is talking about a 2.0 release candidate. I see that there is a branch for it as well.

So now I have questions:

  1. Commits to the master branch are pretty sparse. Is CollectiveAccess actively maintained somewhere else?
  2. Was 1.8 ever released? If so, is that the actual latest stable version?
  3. Is there a roadmap or a timeline for releases?
  4. Are stable releases done by time (ie: quarterly/yearly/etc) or by feature?
  5. My project wants to use pawtucket2 to bring the collection to the public. That means being out on the open internet. How are security vulnerabilities found and fixed?

Thanks for any help in my evaluation.

PS: If an issue needs to have a desired action item, then this ticket's requested action item is "Please update the website, the news site, and the repo README with information regarding the latest stable and development versions as well as with information regarding the release schedule."

@collectiveaccess
Copy link
Owner

What we were calling 1.8 will be released as 2.0, as users weighted in that it was a major release and that should be indicated in the numbering. Active development take place in branches. The master branch will reflect the current release. The dev/php8 branch reflects current 2.0 development. The 2.0 release is currently in testing with several sites and will be released shortly - before 25 December 2024.

Stable releases are made by feature. There has been a long lag since the last major release. We intend to do more frequent feature releases on a six month cycle with the 2.0 version. Maintenance releases for 2.0 will be as-needed and more frequent.

Web sites and readme will be updated when 2.0 is released.

Security vulnerabilities are discovered through testing, user reports and scans with open source and commercial vulnerability scanners.

@eparadis
Copy link
Author

Thank you for explaining the current status and your plans for the year.

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

2 participants