Release 0.10.0 about deptry

[mkniewallner]

In the features, I think that only #357 is worth mentioning, as the other changes are internal ones, and not user-facing changes.

Same in miscellaneous, only #368 is probably worth mentioning (and could maybe be moved to features, although it could be ok to keep it in this section).

For consistency with other entries, we should also drop "feat():" and capitalise the first word.

[fpgmaas]

Thanks for the feedback! Processed your proposed changes :)

[mkniewallner]

Looks good to me 🙂

[lisphilar]

Dear @fpgmaas and @mkniewallner ,
Thank you again for your hard work with this valuable library!
This may be off toppic, but is "version 1.0.0" release (with stable public APIs) planned?

[fpgmaas]

Release published: https://github.com/fpgmaas/deptry/releases/tag/0.10.0
Pypi: https://pypi.org/project/deptry/0.10.0/

[fpgmaas]

Hey @lisphilar! Thanks for you comment. I am afraid that the 1.0.0 release is not currently planned, although it might be something that we could start thinking towards.

"In summary, a 1.0.0 release should be considered when the package is stable, provides all of the essential features, has a stable API, is thoroughly tested, and has received positive user feedback."

I think out of this list the stable API is the one part that is currently lacking; we still make some changes to it, albeit irregularly. I do think that the package is reaching a level of maturity where we are relatively close to achieving this stable API.

Sorry for not being able to provide more clarity on this yet!

[lisphilar]

Thank you for your reply!
Yes, stable API is very helpful for users, but, for developers, maintenance cost is higher than 0.x.x releases actually. I will continue to follow issues including #374. Thank you.