Angband and Ubuntu

[takkaria]

Originally Posted by AnonymousHero

Why are we waiting for three bugs in particular? Aren't there enough bugfixes already in master to release 3.5.1 and then follow up with a 3.5.2 at some point? If there release process is too arduous for this to be practical, then I submit that the release process needs to be revisited and optimized.

Originally Posted by AnonymousHero

But aren't there enough commits/fixes regardless of anything happening in a side branch? Or is Magnate being set up for cherry-picking a huge amount of commits or something? (If the latter is the case, then I think there's an overall issue with the way branching is being handled.)

I don't think there's anything wrong with our release process. No-one is cherry-picking huge numbers of commits and we defined 'enough fixes' at our last devteam meeting as 'when bugs A, B, C ... X, Y & Z were fixed'. They're not all fixed yet, hence no release. FWIW there are 43 other commits on master ready to go, amassed over the last year.

Hang in there, it's almost out

[AnonymousHero]

Originally Posted by takkaria

Hang in there, it's almost out

I usually run from 'master', I was just curious .

[Magnate]

Originally Posted by AnonymousHero

I usually run from 'master'

I think that puts you in a fairly small group of players.

FWIW I think the release process is fine, but it is definitely not push-button - and never will be. To make a half decent release you need to check or update various things manually (changelog, thanks, FAQs) and do invisible but important things like git tagging etc. We got it down to this, which is ok, but definitely something I'd rather not do twice. 3.5.1 will be the last release "before the restructure" - ah good, I'd been wondering what to call it ...

[takkaria]

Originally Posted by AnonymousHero

I usually run from 'master', I was just curious .

I said master - I meant 3.5-release. Oops.