May 5, 2019

Would you release version 1.0.0?

Johannes Lichtenberger @Lichtenberger

Suppose you're working on a free Open Source software and still lack a proper community after years, but you still keep on working... would you release version 1.0.0? I hesitate, because I would love to have feedback before and fix bugs. And I don't know if it makes any difference. I think it was for instance the point where Vue.js took off, but I think that's probably not normal.

I sometimes feel a bit sad, because of all the work put into the project and almost no feedback (but somehow now more than 200 stars on Github, which is a lot in my eyes).

Kind regards
Johannes

  1. 3

    I posted it to hacker news for you:

    https://news.ycombinator.com/item?id=19834681

    I think this is more up their alley...

    1. 1

      Wow, unbelievable... front page :-) thanks so so much

      1. 3

        Dude.. I totally hooked you up. You owe me one :)

        1. 1

          Oh yes, it's crazy :-)

      2. 2

        Another note.. you're probably not capturing this as much as you would like because github doesn't have analytics but you'll probably get 5-10k people checking it out.

        Try to see if you can get a form to subscribe some people to a mailing list on the main page.

        1. 1

          Do you know how I can get users to my discourse forum? I'd love to get more feedback somehow. I'm sure by now a few users might have really checked it out... but so far no one writes about what might have failed, missing/wrong documentation and so on.

        2. 1

          Will do, luckily I added Google Analytics yesterday before your hacker news post ;-)

    2. 1

      Thanks, posted over there, but haven't had so much luck, but thanks so much. With other news I recently gained quiet some Karma, but yeah

  2. 2

    You're crushing it with 200+ stars. I wouldn't pay much mind to it unless you're concerned with the perception that the software is still beta / pre-v1 by your users. I feel that these days devs are significantly more apt to use a valuable library regardless of the current status of the version number.

    If you think it's ready, may as well drop the 1.0 release. If nothing else, it's a notable achievement that could lend itself to some marketing opportunities. Reach out to some blogs and see if any of them will cover it!

    1. 2

      Do you maybe know database blogs? I have to admit, I'm not reading a lot of blogs ;-)

      1. 1

        Nothing off the top of my head, but may be able to leverage something like dev.to

  3. 2

    Release early, release often. Make it clear that it's early and might have rough edges.

    Without users you won't know what the rough edges are and won't be able to prioritize what to fix.

    1. 1

      That's why I released 0.9.1 yesterday, but maybe nobody wants to try software below 1.0? I have no clue. Thanks for the tip :-)

      1. 1

        Marketing and growth is probably the issue.

        Just cut 1.0.0... doesn't hurt to try. No one is going to hold it against you.

        1. 1

          Hm, might simply release it in two weeks or so :-) but I really had no idea that 1.0.0 has so much impact

          1. 1

            This hit Hadoop back in the day and they just quietly called a release 1.0... a lot of corporate execs think < 1.0.0 is semantic and means 'beta'

            1. 1

              Thanks but... for me at least the native JSON stuff is Beta, XML maybe not. But at work we had to do a release which is totally unstable, so... ;-)

  4. 2

    Would you mind sharing the project?

    1. 1

      Thanks for asking :-)

  5. 1

    This comment was deleted a year ago.

  6. 1

    This comment was deleted 7 months ago.

    1. 1

      I'd love to port visualizations to the web for comparing revisions of natively stored XML- and JSON-documents. That said I'm sadly a backend developer and the front-end stuff seems a bit overwhelming

      1. 1

        But I could add lots more sample queries :-)