Mats Lidell writes:
>>>>> Stephen wrote:
Stephen> You committed to the mainline, which broke the packages build
Stephen> completely. It's really important to do this kind of work on
Stephen> the branch.
I'm not sure that is necessary. As I understand it the reason for
doing it in a branch was that we thought a patch to XEmacs.rules was
needed.
The reason for doing anything in a branch is to avoid interrupting
work on the mainline. This is a huge change and hoping that there are
no problems is silly. This does not reflect on you or Uwe in the
slightest. I wouldn't do this work in the mainline, nor would any of
the other core developers.
But I think we have found a way to make the build work without that
patch. So this is a plain package upgrade and I don't think they need
to be done in a branch.
Look in the VM thread started by Giacomo Boffi for another reason why
major upgrades should be done on a branch.
Maybe big updates are vice to handle in a branch but the release
procedure of the distribution does allow for some problems to exist
for a while doesn't it?
Not if it stops the build, which this does.
It's really not that hard to work in a CVS branch once you've set it
up properly (for this kind of task). I did it for many months while
releasing 21.4.
So as can happen with major upgrades not all things have been
checked
in. A few files and folders are missing for the build to work
properly. I believe that Uwe is away for a few days or so so I suggest
we wait for him to come back and check the rest in.
If he's away for a few days, I'll move the broken stuff to the branch
and restore the 1.48 release.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta