this is a good point. Yes, my reasoning was to say, “hey, we fixed this bug that’s existed since the beginning of LG, and if you were relying on this function to produce correct results, well, now you should update and rerun your code”. The fact that we’ve had two such bugs reported and fixed in the past month is both disconcerting and welcome.
(That is to say, the two most recent bugs were errors in CORRECTNESS, which are most insidious, because valid output is provided – it’s just wrong.)
The larger issue for me is that I don’t know who’s using the code, where, and for what purposes, and when we fix a bug like this it could have some impacts I’m unaware of. Perhaps it’s the users’ responsibility to monitor the github repo, but for bugfixes I thought it made sense to post an announcement.
The general sentiment I’m hearing, though, is “nope, too much, don’t do this”, so I’ll refrain from posting bugfixes here (or will try @nilshg’s interesting approach once we hit v2.0.0).
If you’re using LightGraphs, please monitor the repo