The promise I’m referring to, is to “release the code”.
(long version)
I understand the thought process of people not wanting to show how messy their pre-production code is… but that’s why, following semver rules, you mark it as a version “0.x.y”. It’s not an exam, it’s nothing to be ashamed of, anyone who’s written code knows that’s how things work, and it’s on the community to be understanding of this, so the “initial dev” of an open source project should feel confident in releasing a tangled mess, no less no more.
Promising the code, then disappearing without giving a community that’s invested in the project a chance to take over, is what I find fishy.
I’ve nothing to say more on topic. Off topic, people may be quite different and even if objectively there should be nothing bad in releasing pre-production, they may find it sensitive + there might be someone to actively offend for that. I only encountered the former, luckily
I’m mostly with you but “didn’t want to release prematurely” is not a promise, as you can never know when one sees code as matured.
The promise I’m referring to, is to “release the code”.
(long version)
I understand the thought process of people not wanting to show how messy their pre-production code is… but that’s why, following semver rules, you mark it as a version “0.x.y”. It’s not an exam, it’s nothing to be ashamed of, anyone who’s written code knows that’s how things work, and it’s on the community to be understanding of this, so the “initial dev” of an open source project should feel confident in releasing a tangled mess, no less no more.
Promising the code, then disappearing without giving a community that’s invested in the project a chance to take over, is what I find fishy.
I’ve nothing to say more on topic. Off topic, people may be quite different and even if objectively there should be nothing bad in releasing pre-production, they may find it sensitive + there might be someone to actively offend for that. I only encountered the former, luckily