|
|
|
|
|
by interroboink
453 days ago
|
|
I actually prefer the "when it's done" model rather than the "train leaving the station" model, for software like this. I feel it better allows for broad-scope changes, which may touch large swaths of a codebase, to more fully gel/mature before being released. For something that I might only update once every few years anyway (ie: not very security-critical), it seems worthwhile to reduce the overhead of release process/logistics for the developers, letting them spend that time on features/fixes instead. Or maybe there was another model you were suggesting? What do you find non-sane about the current one? |
|
Hopefully the now-impending port to GTK 4 will be a lot smoother and won't be such a disruption to their ability to ship the features they've been working on.