News for hackers. Stuff that matters.
Re:Non-technical security best-practices for open source pro... by cortesoft on Saturday June 05, 2021 @09:09PM (#27409829)
So does number 2 mean you can't ever change your interface?
Re:Non-technical security best-practices for open source pro... by voidfunc on Saturday June 05, 2021 @10:27PM (#27410204)
I think #2 is imprecise in its wording. Break between major versions (though, really, you should only break it for a good reason).

What I am seeing is breaking changes more and more in minor and patch versions, especially since developers are afraid to cut a 1.x so they hide behind the 0.x semantic versioning unstable interface clause.

Re:Non-technical security best-practices for open source pro... by cortesoft on Sunday June 06, 2021 @01:17AM (#27410972)
This would also only seem to matter if you release security patches to older major versions... otherwise those same people still wouldn't get security updates.
Re:Non-technical security best-practices for open source pro... by shkkmo on Saturday June 05, 2021 @11:01PM (#27410396)
I would say, be aware that major inforface changes mean that you might need to support the previous version with security fixes for a long time or leave non-adopters exposed.
Re:Non-technical security best-practices for open source pro... by cortesoft on Sunday June 06, 2021 @01:20AM (#27410980)
Yeah, that was really where my question was trying to get to... what unspoken assumption is being omitted?
Re:Non-technical security best-practices for open source pro... by mro_name on Sunday June 06, 2021 @05:30AM (#27411894)
Use minors to add but beware of bloat. And majors to purge.

Breathe in, breathe out. Like the tides.