On 1/22/07, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
A.J. Rossini writes:
> It's an issue with maintainer stress, dealing with getting upstream
> into XEmacs package repo with minimal problems.
> Simple, easy build tools and patches for such welcome (send such to
> ESS-help list or ESS-bugs list)
Can you be more specific about the problems these tools are supposed
My understanding from what Rodney said at the time was that simply the
effort of copying the code into a checkout of ESS from XEmacs CVS and
doing a test build was costing too much time and effort given the
activity of the ESS project, and his goals for the timeliness of
XEmacs package releases of ESS. Frustration with timeliness (rather,
the lack of it) was further aggravated by the lags imposed by the
package and SUMO release cycles.
You've summarized it well. Basically, we'd like someone to take care
of this for us, as we are resource-short (i.e. I'm stuck at the point
of reading email, no time for any more, with respect to ESS). This
could be done through the use of tools to pull versions out of the ESS
SVN repository and into the XEmacs package repository, or through the
use of a person to do the same (it's a read-able repository).
There are also issues with package release cycle timing, but I suspect
that they are minor.
I don't mean to imply that ESS is the only package with the problem --
I fully recognize that this is a general problem, and we aren't
complaining, just trying to figure out how to do things!
"Commit early,commit often, and commit in a repository from which we can easily
roll-back your mistakes" (AJR, 4Jan05).
XEmacs-Beta mailing list