all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] Wrong dependency headers for Ement v0.4
Date: Thu, 27 Oct 2022 16:18:46 -0400	[thread overview]
Message-ID: <jwva65hqb0u.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <e912cee4-46b3-2b4b-6484-a33bfd72979a@alphapapa.net> (Adam Porter's message of "Thu, 27 Oct 2022 12:46:37 -0500")

> Well, it's good that it was finally discovered.  :)

And fixed, even!

>>> Given that, would it be possible to have ELPA build from a separate branch?
>>> That's how I organize some of my other packages, with a "stable" branch and
>>> a master branch.  If ELPA pulled from a "stable" branch, I could push a fix
>>> to that while the next major version is still in development.
>> We can also do that, yes, using the `:release-branch`.
>
> Okay, that sounds good to me.  Please see the attached patch to
> elpa-packages, which sets the release-branch to "stable".

Done, thanks.

> Will this patch cause the package to be rebuilt for v0.4, or do I need to
> make a v0.4.1 release to trigger that?

There's already a 0.4 package, and by design, packages never(!) get
rebuilt, so you'll need to change `Version:`, yes.
[ And currently, changes on the release branch are only pulled as
  a side-effect of pulling changes from the devel branch, so if you only
  commit to the release branch, the package may wait for a while until
  it's actually released.  :-(  ]


        Stefan




  reply	other threads:[~2022-10-27 20:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <85sfjfa7v0.fsf@elpa.gnu.org>
2022-10-24 15:44 ` [ELPA] Wrong dependency headers for Ement v0.4 Adam Porter
2022-10-24 20:51   ` Stefan Monnier
2022-10-27 17:46     ` Adam Porter
2022-10-27 20:18       ` Stefan Monnier [this message]
2022-10-27 20:28         ` Adam Porter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwva65hqb0u.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=adam@alphapapa.net \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.