#lifecyclemanagement — Public Fediverse posts

✨Bringing light to #LifeCycleManagement ✨

Digital preservation is like a journey.

From ingest to versioning, or even batch export and disposal, every stage builds on the last.

👉CPP-029, CPP-021, CPP-006, and CPP-018 help you manage data throughout its lifecycle: tiny.cc/cpp-desc

#EOSCEDEN #CPPs

✨Bringing light to #LifeCycleManagement ✨

Digital preservation is like a journey.

From ingest to versioning, or even batch export and disposal, every stage builds on the last.

👉CPP-029, CPP-021, CPP-006, and CPP-018 help you manage data throughout its lifecycle: tiny.cc/cpp-desc

#EOSCEDEN #CPPs

Start-ups win early adopters. Scaling means crossing the chasm to the mainstream, and the mainstream doesn’t forgive sloppiness. Discipline across the customer journey is what carries you over. 🌉
#ScalingUp #CustomerExperience #LifecycleManagement

http://branici.ro/2025/09/28/scaling-customer-success/

At work I have a monorepo with a bunch of helm charts in it.
The LCM for this repo is garbage - I wrote it a few years ago not really knowing what I was doing, but also knowing it was a temporary thing.
Turns out it’s not so temporary.

The company is looking to move to trunk-based development and I’m looking to redo the LCM of this repo.

Specifically this TBD: https://trunkbaseddevelopment.com/
We want to be able to say “we are doing this” and point at an industry way of doing things, rather than looking at something home grown or modified.

TBD makes sense to me, I’m pretty sure I understand it.

But- the charts on the repo are released altogether monthly (looking to change this, but anticipating another year or more before being able to do so), there are two breaking changes a year.

If I need to patch an old (supported) version, I might not be able to commit it to trunk and cherry-pick back to a relevant release branch because feature flags are hard to impossible in Helm (specifically in the way we use a library chart to provide 99% of the templating).

Am I “allowed” to commit/PR directly to the release branch in this case?
I know I technically can, but I can’t find what is idiomatic TBD in this situation.

#branchingstrategies #trunkbased #trunkbaseddevelopment #git #lifecyclemanagement

At work I have a monorepo with a bunch of helm charts in it.
The LCM for this repo is garbage - I wrote it a few years ago not really knowing what I was doing, but also knowing it was a temporary thing.
Turns out it’s not so temporary.

The company is looking to move to trunk-based development and I’m looking to redo the LCM of this repo.

Specifically this TBD: https://trunkbaseddevelopment.com/
We want to be able to say “we are doing this” and point at an industry way of doing things, rather than looking at something home grown or modified.

TBD makes sense to me, I’m pretty sure I understand it.

But- the charts on the repo are released altogether monthly (looking to change this, but anticipating another year or more before being able to do so), there are two breaking changes a year.

If I need to patch an old (supported) version, I might not be able to commit it to trunk and cherry-pick back to a relevant release branch because feature flags are hard to impossible in Helm (specifically in the way we use a library chart to provide 99% of the templating).

Am I “allowed” to commit/PR directly to the release branch in this case?
I know I technically can, but I can’t find what is idiomatic TBD in this situation.

#branchingstrategies #trunkbased #trunkbaseddevelopment #git #lifecyclemanagement

Sentinel Tip - Set Up Data Retention Policies: Configure data retention policies to comply with regulatory requirements. Retention policies help in managing data lifecycle and compliance. Keep data you query regularly in interactive (hot) tier and archive or export the rest to control costs. #DataRetention #Compliance #LifecycleManagement

@mttaggart what a great source to Lear from
#infosec #ransomeware
No MFA on terminal servers, no exfiltration monitoring (or too late) and a hodgepool of old systems, no #lcm #lifeCycleManagement
They do have backups but cant restore them cause the systems are eol.
I dont think any of us in this circumstances would have done much better

Een van mijn pet-peeves is #lifecyclemanagement: het proces waarbij men als organisatie onder meer de support lifecycle van alle gebruikte producten in kaart heeft en er *tijdig* vervanging/upgrades worden gepland en uitgevoerd.

De volgende belangrijke is #Windows Server 2012 (R2) waarvan de Extended Support op 10 oktober 2023 verloopt.

Als je nog geen plannen had, BEGIN DAAR DAN NU MEE! Lees hier de opties: https://learn.microsoft.com/en-us/lifecycle/announcements/windows-server-2012-r2-end-of-support

#WeekITtip #SimplifyNow

Een van mijn pet-peeves is #lifecyclemanagement: het proces waarbij men als organisatie onder meer de support lifecycle van alle gebruikte producten in kaart heeft en er *tijdig* vervanging/upgrades worden gepland en uitgevoerd.

De volgende belangrijke is #Windows Server 2012 (R2) waarvan de Extended Support op 10 oktober 2023 verloopt.

Als je nog geen plannen had, BEGIN DAAR DAN NU MEE! Lees hier de opties: https://learn.microsoft.com/en-us/lifecycle/announcements/windows-server-2012-r2-end-of-support

#WeekITtip #SimplifyNow

Proud owner of a #Fairphone
#RightToRepair #LifecycleManagement

Even if I use @murena myself on my #FP3 having the possibility to receive updates till the year 2026 is outstanding

That's #sustainability

https://www.golem.de/news/smartphone-fairphone-3-bekommt-android-13-2304-173414.html

Dear fellow #infosec #itsec #ciso #cissp #security and other practitioners:

Are there any ideas or #BestPractices for managing, #logging and alerting #K8s #Kubernetes in #AssetManagement #Assets #CMDB? Should I log every pod spun up? Should I log every request and the associated pod? Should I create CIs for every pod and retire them quite soon?

Any hints are appreciated, even more complete guidelines. Thank you.

#LifeCycleManagement

Dear fellow #infosec #itsec #ciso #cissp #security and other practitioners:

Are there any ideas or #BestPractices for managing, #logging and alerting #K8s #Kubernetes in #AssetManagement #Assets #CMDB? Should I log every pod spun up? Should I log every request and the associated pod? Should I create CIs for every pod and retire them quite soon?

Any hints are appreciated, even more complete guidelines. Thank you.

#LifeCycleManagement