home.social

#release-management — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #release-management, aggregated by home.social.

fetched live
  1. 🚀 La gestión de releases es clave para lanzar software de calidad. Conoce el ciclo de vida, estrategias y herramientas que todo desarrollador debe dominar. 💻✨

    Lee más 👉 soloingenieria.org/ingenieria-

    Imagen creada con IA.
    #GestiónDeReleases #IngenieríaDeSoftware #DesarrolloDeSoftware #DevOps #ReleaseManagement

  2. Un release mal gestionado no solo afecta al software, afecta la confianza del usuario. 🎯 La diferencia entre un buen equipo y uno excelente está en cómo planifica sus entregas.

    #GestiónDeReleases #IngenieríaDeSoftware #DesarrolloDeSoftware #DevOps #ReleaseManagement

  3. Urgh, doing public releases on an official public registry, but not providing any tagged commits.😑

    How should I know, which commit belongs to a release then!?

    We've officially entered the era of software develsloppers.

    #SoftwareDevelsloppers #Slop #NoNotAISlop #Releasemanagement #OpenSource

  4. Urgh, doing public releases on an official public registry, but not providing any tagged commits.😑

    How should I know, which commit belongs to a release then!?

    We've officially entered the era of software develsloppers.

    #SoftwareDevelsloppers #Slop #NoNotAISlop #Releasemanagement #OpenSource

  5. Blog: WooCommerce Brands rollout
    With WooCommerce 9.4, WooCommerce Brands is getting rolled out to a cohort (5%) of installs. If you do not want to participate in this change set the option woocommerce_remote_variant_assignment to a higher value, e.g. 111 While this is a good feature, it can break your existing brands solution as it did in my case on […] …
    #ecommerce #ReleaseManagement #WooCommerce #WordPress
    bramesposito.com/blog/2025/01/

  6. #CaseStudy - #Slack has developed a custom #KubernetesOperator to address limitations in managing StatefulSet deployments.

    Introducing the Bedrock Rollout Operator - written to offer improved control & features for deploying stateful applications in Kubernetes clusters: bit.ly/46C7HTY

    #InfoQ #Kubernetes #Deployment #ReleaseManagement

  7. - has developed a custom to address limitations in managing StatefulSet deployments.

    Introducing the Bedrock Rollout Operator - written to offer improved control & features for deploying stateful applications in Kubernetes clusters: bit.ly/46C7HTY

  8. 🗓️ Our orcharhino Ask Me Anything Workshop is tomorrow! 🗓️

    Join us tomorrow at 4 p.m. CEST for a unique opportunity to engage directly with our developers, consultants, and the orcharhino team. Feel free to submit your questions in advance.

    Register now: orcharhino.com/en/events/orcha

    #orcharhino #datacenter #automation #patchmanagement #releasemanagement #workshop #freeworkshop

  9. 🗓️ Our orcharhino Ask Me Anything Workshop is tomorrow! 🗓️

    Join us tomorrow at 4 p.m. CEST for a unique opportunity to engage directly with our developers, consultants, and the orcharhino team. Feel free to submit your questions in advance.

    Register now: orcharhino.com/en/events/orcha

    #orcharhino #datacenter #automation #patchmanagement #releasemanagement #workshop #freeworkshop

  10. In the dynamic sphere of Information Technology, I find myself increasingly drawn to the 'less glamorous' aspect of stability. Here are a few instances that illustrate this preference:

    1. The allure of a Linux distribution like Debian, which prioritizes core functionality and stability over making headlines with experimental features. It's heartening to see Debian providing a solid foundation for others to innovate upon.

    2. The prudence in a software release cycle that's paced at six months, allowing for meticulous testing with multiple release candidates before an official launch. This approach often unveils well-architected software, even in its 'alpha' phase, whereas some 'production-ready' software necessitates frequent bug fixes.

    The common narrative equates rapid releases with innovation. However, the more I explore this, the more I discern the pitfalls of such a fast-paced cycle. It not only burdens downstream stakeholders but also creates a ripple effect across the software supply chain, manifesting issues of a significant magnitude in our daily lives.

    Imagine a near-future where daily updates become a norm for not just our computers and mobile phones, but extend to our cars 🚗, home appliances 🏡, and even farming equipment 🚜. Even if each update process is streamlined to a minute, the cumulative time and effort required could be substantial. (now what if i tell you its far closer then you can imagine)

    Are we truly prepared for such a hyper-connected, software-driven reality where updates are incessant?

    Would love to hear your thoughts on how we might find a sweet spot between nurturing innovation and maintaining stability in our tech-driven world?

    Hastag soup:
    #SoftwareDevelopment #ITIndustry #TechnologyTrends #Innovation #Stability #ReleaseManagement #SoftwareSupplyChain #softwareSecurity #informationSecurity #appsec #infosec

  11. In the dynamic sphere of Information Technology, I find myself increasingly drawn to the 'less glamorous' aspect of stability. Here are a few instances that illustrate this preference:

    1. The allure of a Linux distribution like Debian, which prioritizes core functionality and stability over making headlines with experimental features. It's heartening to see Debian providing a solid foundation for others to innovate upon.

    2. The prudence in a software release cycle that's paced at six months, allowing for meticulous testing with multiple release candidates before an official launch. This approach often unveils well-architected software, even in its 'alpha' phase, whereas some 'production-ready' software necessitates frequent bug fixes.

    The common narrative equates rapid releases with innovation. However, the more I explore this, the more I discern the pitfalls of such a fast-paced cycle. It not only burdens downstream stakeholders but also creates a ripple effect across the software supply chain, manifesting issues of a significant magnitude in our daily lives.

    Imagine a near-future where daily updates become a norm for not just our computers and mobile phones, but extend to our cars 🚗, home appliances 🏡, and even farming equipment 🚜. Even if each update process is streamlined to a minute, the cumulative time and effort required could be substantial. (now what if i tell you its far closer then you can imagine)

    Are we truly prepared for such a hyper-connected, software-driven reality where updates are incessant?

    Would love to hear your thoughts on how we might find a sweet spot between nurturing innovation and maintaining stability in our tech-driven world?

    Hastag soup:
    #SoftwareDevelopment #ITIndustry #TechnologyTrends #Innovation #Stability #ReleaseManagement #SoftwareSupplyChain #softwareSecurity #informationSecurity #appsec #infosec

  12. Excited to be speaking at next week 🇬🇧 and sharing how we gained into our CI/CD pipeline.
    👉 lnkd.in/d9rexfx4

    RSVP at lnkd.in/duNHFF8c,
    and the great news are that as a speaker I get to share with my friends a 25% discount! Just use promo code SEEMESPEAK23 😍

  13. Excited to be speaking at #DevoxxUK next week 🇬🇧 and sharing how we gained #observability into our CI/CD pipeline.
    👉 lnkd.in/d9rexfx4

    RSVP at lnkd.in/duNHFF8c,
    and the great news are that as a speaker I get to share with my friends a 25% discount! Just use promo code SEEMESPEAK23 😍
    #cicd #cicdpipelines #releasemanagement #jenkins #devoxx

  14. Had a release failed because the one of the prod-only k8s deployment YAML files had a space missing on one line causing an indentation fail.

    1 missing character forced a release to fail, trigging a rollback. Couldn't fix the issue on the fly due to change controls.

    #DevOps #ReleaseManagement

  15. Had a release failed because the one of the prod-only k8s deployment YAML files had a space missing on one line causing an indentation fail.

    1 missing character forced a release to fail, trigging a rollback. Couldn't fix the issue on the fly due to change controls.

    #DevOps #ReleaseManagement

  16. Lately I have been exploring some ideas on building a "release monitoring tool" leveraging github.com/updatecli/updatecli.

    Technically speaking, we could monitor more than releases but my intent is to be better understand the stability of some of the projects I am working on so Feel free to DM, if this topic interests you too.

  17. Lately I have been exploring some ideas on building a "release monitoring tool" leveraging github.com/updatecli/updatecli.

    Technically speaking, we could monitor more than releases but my intent is to be better understand the stability of some of the projects I am working on so Feel free to DM, if this topic interests you too.

    #devops #gitops #monitoring #releasemanagement #platformengineering