3 ms·

The answer doesn't match the question. The question is, "How do I know when to release 1.0.0?", whereas the answered question seems to me more, "How do I know i

The answer doesn't match the question. The question is, "How do I know when to release 1.0.0?", whereas the answered question seems to me more, "How do I know if I already should have released 1.0.0?" It's a statement about hindsight, not planning. IE, if I'm wondering if can I make a 1.0.0 release even if I think the project won't have users until, 1.4.x but 1.0.0 represents a logical core, that scenario is not addressed by the "should probably already be 1.0.0" after the fact tests provided.

coldtea 11y ago
>It's a statement about hindsight, not planning. It's about what to do with your code as it is right now -- at every now. >IE, if I'm wondering if can I make a 1.0.0 release even if I think the project won't have users until, 1.4.x but 1.0.0 represents a logical core, that scenario is not addressed by the "should probably already be 1.0.0" after the fact tests provided. I don't think project authors should be worried about making an 1.0.0 in advance, that is, before they have written the code and releases several versions. At which point it comes down to the "hindsight" answer as a heuristic. E.g. "if I'm wondering if can I make a 1.0.0 release even if I think the project won't have users until, 1.4.x" -- there's just no way to knowing whether the project will "have users" until it has.