Conversation

Notices

1. Embed this notice
   洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Sunday, 31-Mar-2024 11:26:34 JST 洪 民憙 (Hong Minhee)

   A pre-released version of #Fedify is now available on #npm!

   https://www.npmjs.com/package/@fedify/fedify/v/0.5.0-dev.90

   • Embed this notice
     洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Sunday, 31-Mar-2024 19:42:33 JST 洪 民憙 (Hong Minhee)

     in reply to

     • Mark Gardner

     @mjgardner If you want to publish a pre-release version to npm, it's simple. Just use a pre-release version (in accordance with the definition of Semantic Versioning, e.g., 1.2.3-dev.123) and tag it with anything other than latest (you can specify a tag with npm publish --tag option).

   • Embed this notice
     Mark Gardner (mjgardner@social.sdf.org)'s status on Sunday, 31-Mar-2024 19:42:34 JST Mark Gardner

     in reply to

     • Fediverse Report

     @hongminhee @fediversereport How do you “pre-release” open source software?

   • Embed this notice
     洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Sunday, 31-Mar-2024 19:53:10 JST 洪 民憙 (Hong Minhee)

     in reply to

     • Mark Gardner

     @mjgardner Oh, right, the pre-release I'm talking about is a pre-release as defined by Semantic Versioning, which means it's not guaranteed to be stable.

   • Embed this notice
     Mark Gardner (mjgardner@social.sdf.org)'s status on Sunday, 31-Mar-2024 19:53:11 JST Mark Gardner

     in reply to

     @hongminhee But… it was already *released.* It’s in a public source code repository. You can download it.

     I think you mean a “development” release.

   • Embed this notice
     洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Sunday, 31-Mar-2024 20:02:08 JST 洪 民憙 (Hong Minhee)

     in reply to

     • Mark Gardner

     @mjgardner I don't think so, because revealing that a version is unstable by notation is not a bad idea for many users, it just might not be what you need.

   • Embed this notice
     Mark Gardner (mjgardner@social.sdf.org)'s status on Sunday, 31-Mar-2024 20:02:09 JST Mark Gardner

     in reply to

     @hongminhee It’s a stupid term for it. https://semver.org/#spec-item-9

   • Embed this notice
     clacke (clacke@libranet.de)'s status on Friday, 26-Apr-2024 22:57:09 JST clacke

     in reply to

     • Mark Gardner

     @mjgardner @hongminhee It's not unusual and it's not new to distinguish official releases and versions that are not quite there yet.

     Whether it's an alpha, beta, dev version or pre-release it's pretty clear to everyone what it means. There will be a Release, this is not it.

   • Embed this notice
     Mark Gardner (mjgardner@social.sdf.org)'s status on Friday, 26-Apr-2024 22:57:10 JST Mark Gardner

     in reply to

     @hongminhee I meant that “pre-release” is the stupid term. Call it “development” or “unstable.”

   • Embed this notice
     clacke (clacke@libranet.de)'s status on Saturday, 27-Apr-2024 08:55:37 JST clacke

     in reply to

     • Mark Gardner

     @mjgardner Your point is that everything is released all the time because anyone can check out a commit and get the product.

     That's not how most software people use the term release.

     @hongminhee

   • Embed this notice
     Mark Gardner (mjgardner@social.sdf.org)'s status on Saturday, 27-Apr-2024 08:55:38 JST Mark Gardner

     in reply to

     • clacke

     @clacke @hongminhee This is for both of you