Re: 22.0 Release Status: Important news

mb> XEmacs 21.2 CVS is shippable now, modulo a few little things mb> like NEWS files and other documentation. SJT> No, it's not. It will be Feb 1 at the earliest before I will be ready SJT> to think about shipping this. I don't really have a good idea what it SJT> is I have committed to shipping yet, let alone documents written about it. mb> I suggest you not bother and simply ship what we have on mb> Feb. 1. SJT> Now _this_ is a truly crackpot idea! :-) You realize that all open SJT> source development will come to a stop, perhaps for years, as the SJT> entire community has a collective heart attack when a major app, an SJT> Emacs, yet, is released a month ahead of schedule? Of course you misunderstood me. I didn't mean shipping on Feb. 1, I mean seeing what we have on Feb. 1 and shpping THAT. Later. In practice we would intend to ship March 1, but in fact ship April 1 -- business as usual. mb> But Stephen, you're doing most of the work, so you get to call mb> the shots. SJT> Realistically, they're already distracted. The only sensible thing to SJT> do is damage control. My feeling is open the new devel branch now, so SJT> there's a place I can arbitrarily divert patches to without getting SJT> lynched. If you really want me to do the CVS work, I'll start on it now, but I prefer "wait and see" wrt a new branch. SJT> Do we know how to move the head of trunk to that branch? I haven't decided how to this yet. Leave it to me. SJT> When should we do that? martin> I suggest we cut the branch for 21.4 on Feb. 1. SJT> March 1. That's the scheduled date, and I see no reason to advance SJT> it. I would like to have a testing period with widgets and pdump in, SJT> even if we decide to default them off. We shouldn't have repeated CVS churn, so whenever we create a new branch for the new stable version, we should also move development to the trunk.