> From: Sean Whitton <[email protected]> > Cc: [email protected], [email protected], > [email protected], [email protected] > Date: Mon, 29 Jun 2026 16:19:50 +0100 > > Eli Zaretskii [27/Jun 7:56pm +03] wrote: > > I think you underestimate the effort needed to produce the tarball, > > test it and upload it. Doesn't it take a few hours? > > I'm not sure yet because the only time I've done it was the very first > time. But I noticed several things ripe for scripting, and I think I > can bring it down to ~1h (with most of that time spent waiting).
It takes me around 1.5 -- 2 hours, but it could be that the system on which I was doing that is a bit weak. E.g., I couldn't run parallel Make with more than 4 jobs simultaneously, when building the pretest. However, other parts of the job are inherently single-threaded. > > How much time do you have to work on Emacs on any given day? > > Well, that varies a lot. My point is that if making a pretest tarball takes 2 hours, it could very well exhaust whatever time one has on that day. Which means all the other jobs to be done on that day will need to wait. > >> Maybe backporting *from* Jane Street's branch *to* Savannah's branch > >> would allow us to overcome the problem Stefan describes of not being > >> able to give the fixes enough testing? > > > > Not sure what will this solve. We still need to be very much involved > > in the examination of the fixes and the decisions to which branch(es) > > to backport them. This must be a job of the Emacs maintenance team, > > so if Spencer or someone else volunteers to do it, they will need to > > become part of the team and take the responsibility for doing this and > > communicating with the rest of the team as part of the decision what > > to do with each fix. > > Right. My idea is just that this gets us the testing. It could do that, yes.
