> Look, I'm going to side with Theo on that one. > > There are lots of *big* issues to fix each release. It doesn't look like > it from outside, but we have show-stoppers. > > Each release, we refine the process. > > This release, we cut down on the number of non-critical commits right up > to the lock. > > So that the release goes smoother. > So that things go faster. > You can help by testing the snapshots, telling what does not work, etc. > > As soon as the release is past, it will be `business as usual', and of > course, a lot of `minor' patches are going to happen.
> Seriously, the release work is gigantic. There are choices to be made. > If you don't like the current choices, tough. Well maybe the issue is that, except of the developers, nobody knows how you do make a release or what a gigantic work it is? I wont piss off anybody, it will be a gigantic task and I can imagine it (hopefully) because of some projects as well but except to tell anybody "you can't have both" a "we do not have the manpower to do this" would be more truthly? It's no shame to admit there not enough res. available to do things. Anyway I wont argue and I thank you very much for any effort! (and I seriously mean it). :) And this is offtopic but: In case pcc gets "productiv" do you think this may would speed things up. Except manpower what else is the bottleneck currently (related to the ports)? Kind regards, Sebastian
