Every developer or dev team can relate -
Uncategorized
36
Posts
26
Posters
8
Views
-
Every developer or dev team can relate -
I think I just pushed version 0.12.9998
-
Every developer or dev team can relate -
@Natasha_Jay #hugo 364 releases since 2013 and still hasn’t gotten to 1.0 😂🤣 Little did users know that fast referred to the release and deprecation support cycle
-
Every developer or dev team can relate -
-
Every developer or dev team can relate -
@Natasha_Jay "Default version: Shouldn't contain breaking changes by definition, but every once in a while definitely will."
-
Every developer or dev team can relate -
@Natasha_Jay the real semantic versioning
-
@disorderlyf @Natasha_Jay (possible) joke aside, yes, it's not unthinkable; I have had, more than once, to force myself to release version 1.0.0 despite inner voices screaming "but shouldn't we do this first? And also that? And those three other things we still have no idea how to even design? We're not ready for 1.0! <wayne's world voice> We're not worthy! We're not worthy!"
@mrrmot @disorderlyf @Natasha_Jay I've used a package at version 0.02 in production, it did the job well with no issues, it genuinely should have been 1.0
-
@Natasha_Jay I'm running Emacs 30.2, which because I remember my history, I know is secretly Emacs 1.30.2. (RMS lopped the 1. off the front some time in the 1980s.)
@wollman @Natasha_Jay the unixen all did this for a while, iirc
-
Every developer or dev team can relate -
@Natasha_Jay This suggests a LinkedIn versioning scheme, with a single number, incremented on every release with a note saying “I’m proud to announce”
-
Every developer or dev team can relate -
@Natasha_Jay looks at one using CalVer woaw they're so proud of their proejct
-
@Natasha_Jay looks at one using CalVer woaw they're so proud of their proejct
@freeplay@wetdry.world @Natasha_Jay@tech.lgbt also explains why so many projects are 0.XX.XXX nowadays
-
Every developer or dev team can relate -
Major version should be the shame release because you couldn't think of any solution that didn't break back compatibility so you forced a migration on all of your users.
However, this is probably the "current state" slide and semver is the "ideal state" slide.
-
Where’s the imaginary part of the version number? 🤔
@fiee :
That's where you add a plugin framework so you can blame anything that breaks on integrations owned by others.
-
I think I just pushed version 0.12.9998
@benpate :
you must own a critical python library. -
undefined paoloredaelli@mastodon.uno shared this topic on
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@Lyra ma le nostre sono più belle, e si possono cambiare ogni giorno.
-
@francina1909 come siamo povere, nemmeno una Balenciaga originale abbiamo!
-
@quillmatiq@mastodon.social I know that image was meant to be reflective of the ATProto dev landscape, but you're really underselling the variety of applications in that "Fediverse" catch-all bucket :smile:
-
@Otttoz e non che ci lamentavano per i 2 centesimi dei sacchetti della frutta al supermercato. Oggi andrebbero presi a stock e rivenduti su eBay 😂
-
@Lyra io pure a marchio Coop 😂
-
Came to this realization because of standard.site.
After it's baked into Bridgy Fed, both my micro- and macroblogs are sent to the Fediverse via a single account that supports multiple types. As we add more lexicons, that expands the number of types I can send via that one account.
-
Ddl antisemitismo: quando la politica decide quali opinioni sono legali
-
RE: https://mastodon.social/@quillmatiq/116013895130574256
One thing I left out of my The Everything Account piece was a whole section on Bridgy Fed.
Short version: As Bridgy Fed adds more lexicons, it makes the Atmosphere the most versatile and data-owning Fediverse instance in the open social web.
Perhaps in a future piece 😉
