Re: xemacs-packages repo not updated for latest gnus?
Mats Lidell wrote:
>>>>> Mike Kupfer <mike.kupfer(a)xemacs.org>
writes:
> What I'm hazy on is whether the top-level commit/push should be done
> as a matter of course when the new package tarball is published, or
> if the package maintainer is supposed to email Norbert to ask him to
> do it. (I think the former makes more sense.)
I think the process is that you mail Norbert when you have committed a
package. He then updates the package Makefile and ChangeLog and
commits that and then finally commits on the top level the package
together with possibly other packages that are ready.
What I find confusing is that a new package tarball has been built and
posted for download. So presumably Norbert already knows that I pushed
something. I had expected that the commit and push to the top-level
repo in Bitbucket would happen as part of that publication process.
If there's value in separating those two things (publishing the new
tarball and updating the top-level repo), I can certainly live with
sending a separate request to update the top-level repo. But at the
moment I don't see any value in having them separate operations.
cheers,
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta