You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can we say that the project is Dead now? (February 2023)
Description
I was updating a system that uses Docz and I needed to update the tool for security issues in some of the dependencies used by this package, so I tried to do it to the latest version, but it seems that the latest version is from June 2022, and I searched in the Issues reported here and found this:
Where the autor said that is going to be a new version since last year, and also the warning that exist in the README it sends you to the new branch that has the latest commits from 5 months ago, all commits are from September 2022 and before that it goes back to April 2022.
There are also issues like this where there are no answer from the maintainers of the project:
Wondering if it's not better to mark the project as dead / unmaintained and avoid people to depend on it being clear in the README the possible alternatives.
Thanks for reading.
The text was updated successfully, but these errors were encountered:
Question
Can we say that the project is Dead now? (February 2023)
Description
I was updating a system that uses Docz and I needed to update the tool for security issues in some of the dependencies used by this package, so I tried to do it to the latest version, but it seems that the latest version is from June 2022, and I searched in the Issues reported here and found this:
#1634
Where the autor said that is going to be a new version since last year, and also the warning that exist in the README it sends you to the
new
branch that has the latest commits from 5 months ago, all commits are from September 2022 and before that it goes back to April 2022.There are also issues like this where there are no answer from the maintainers of the project:
#1735
Wondering if it's not better to mark the project as dead / unmaintained and avoid people to depend on it being clear in the README the possible alternatives.
Thanks for reading.
The text was updated successfully, but these errors were encountered: