Hacker News new | past | comments | ask | show | jobs | submit login

If there are no commits, maybe that means it is finished, stable, reliable?

I would like more projects to be without commits and just work.

I don't understand why there must always be new commits if everything already works.




There are commits, but no release, it's very frustrating if you depend on any of those commits, and there are no one available to cut a new version, or to pass on the torch.

For four years there was commits to the beanstalkd project, but no release, it took about a year after the issue was first raised until someone appeared and a maintainer was found: https://github.com/beanstalkd/beanstalkd/issues/399


Pipenv isn't stable and reliable yet though, at least compared to pip+venv. The tooling is really handy and it makes it in theory easier to write Python code, but in practice there is still work to be done.


This is a good question. I have wondered the same thing about software in general. In this specific case, though, there are 313 open issues and 33 pull requests. So people are finding bugs in the current version (and fixing them).


You look at the issues list to see if this is the case.

This project has 313 open issues. No, everything’s does not already work.


Because resumes aren't made by maintaining existing well-working software.


there are almost 700 commits to master since the latest release.


But there are commits.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: