pekdon ramblings of a northern geek

pekwm release history

2 min read

pekwm-0.3.0 has been released and includes quite a bit of changes compared to the previous pekwm-0.2.1 not to speak of whats still in some distributions that being pekwm-0.1.18.

These releases got me thinking about the impact the release frequency has on software.

First, lets start of with the not so impressive pekwm release history:

  • 0.3.0, 2022-01, 13 month since 0.2.1.
  • 0.2.1, 2021-12, 1 month since 0.2.0.
  • 0.2.0, 2021-10, 11 months since 0.1.18.
  • 0.1.18, 2020-11, 90 months since 0.1.17.
  • 0.1.17, 2013-05, 6 months since 0.1.16.
  • 0.1.16, 2012-11, 3 months since 0.1.15.
  • 0.1.15, 2012-08, 8 months since 0.1.14.
  • 0.1.14, 2011-12, 6 months since 0.1.13.
  • 0.1.13, 2011-06, 14 months since 0.1.12.
  • 0.1.12, 2010-03, 10 months since 0.1.11.
  • 0.1.11, 2009-05, 4 months since 0.1.10.
  • 0.1.10, 2009-01, 1 month since 0.1.9.
  • 0.1.9, 2008-12, 2 months since 0.1.8.
  • 0.1.8, 2008-10, 2 months since 0.1.7.
  • 0.1.7, 2008-08, 15 months since 0.1.6.
  • 0.1.6, 2007-05, 13 months since 0.1.5.
  • 0.1.5, 2006-04, 2 months since 0.1.4.
  • 0.1.4, 2006-02, 32 months since 0.1.3.
  • 0.1.3, 2003-06, 8 months since 0.1.2.
  • 0.1.2, 2002-10, 4 days since 0.1.1.
  • 0.1.1, 2002-10, second pekwm release.

As the above list shows, the release frequency have been quite irregular to say the least and having releases drag behind have caused a lot of users having to run the development version for a smooth experience.

So, how often should release be made? As with most things I guess there’s no answer that will fit all software but let’s list some of the pros with frequent and infrequent releases.

Frequent releases:

  • Time from bug fix to release is short.
  • Less changes included per release, lower risk.
  • Distribution lag behind, but probably is less annoying.

Infrequent releases:

  • Latest release does not include recent fixes and features.
  • More changes included per release, higher risk.

I think software maturity and current development pace should be key factors when deciding on what release cadence to have unless opting for a fixed cadence which more and more projects seem to adopt these days.

Me, on the other hand, probably should get my act together and get some sort of regularity to both pekwm maintenance and releases.