Hi all, So … I just came back from a little time-out … so I had a gut feeling, that a version of „4.0.0-inclubating“ causes issues and I tried to find confirmation for that. I do know things change, and things that were bad can turn out to become best practice. So, it’s always good to challenge your own beliefs.
So it is true that a version of 4.0.0-incubating has its downsides compared to a pure numeric one. * Version ranges don’t work correctly with them * OSGI has it’s issues with them But I guess in the case of BifroMQ, both of these drawbacks aren’t as severe as for example in my own favorite project: Apache PLC4X. There we do have people using OSGI and I am sure we have people using version ranges. So, I just wanted to loop this back to you. Also did I want to point out that just because you found projects doing something the same way you were intending to, that doesn’t necessarily mean that it’s considered best practice or even allowed. Unfortunately, we’ve seen that several times before, that one (most polling) project does something. As they didn’t ask or discuss things publicly, none of their mentors noticed. But then, other projects use this pattern as confirmation that it’s allowed. Looking at TLPs I would consider pretty mature, but please don’t use other podlings as reference. Not seldomly that even resulted in bringing the spotlight on things that ended up with all podlings needing to drop that pattern. The last time I remember something like that was when I questioned using some AI based tool for „free community support“. Chris
