[ELPA] Use :release-branch for plz.el

[ELPA] Use :release-branch for plz.el

[Adam Porter]

[-- Attachment #1: Type: text/plain, Size: 410 bytes --]

Hi Stefan, Philip, et al,

Please see the attached patch which sets the release branch for plz.el. 
This will allow me to make small, bug-fix version releases from the 
stable branch while the next version is in development on the master branch.

BTW, after having done this for a few packages now, this seems to me to 
be the best practice.  It might be worth recommending this for new packages.

Thanks,
Adam

[-- Attachment #2: 0001-elpa-packages-plz-release-branch-stable.patch --]
[-- Type: text/x-patch, Size: 830 bytes --]

From f5541803a174f677e703d921b875e7875da19662 Mon Sep 17 00:00:00 2001
From: Adam Porter <adam@alphapapa.net>
Date: Sat, 16 Dec 2023 06:59:01 -0600
Subject: [PATCH] * elpa-packages: (plz) :release-branch "stable"

This allows bug-fix versions to be released from "stable" while the
next stable release is in development on "master".
---
 elpa-packages | 1 +
 1 file changed, 1 insertion(+)

diff --git a/elpa-packages b/elpa-packages
index 612bc676cd..ffa211b80f 100644
--- a/elpa-packages
+++ b/elpa-packages
@@ -550,6 +550,7 @@
   :manual-sync t)
  (pinentry		:url "https://github.com/ueno/pinentry-el.git")
  (plz                 	:url "https://github.com/alphapapa/plz.el.git"
+   :release-branch "stable"
   :ignored-files ("LICENSE")
   :doc "README.org")
  (plz-see		:url "https://github.com/astoff/plz-see.el"
-- 
2.30.2

Re: [ELPA] Use :release-branch for plz.el

[Philip Kaludercic]

Adam Porter <adam@alphapapa.net> writes:

> Hi Stefan, Philip, et al,
>
> Please see the attached patch which sets the release branch for
> plz.el. This will allow me to make small, bug-fix version releases
> from the stable branch while the next version is in development on the
> master branch.

Thanks, I have applied and pushed the patch.

> BTW, after having done this for a few packages now, this seems to me
> to be the best practice.  It might be worth recommending this for new
> packages.

I have no real opinion on this, other than that it might be
unnecessarily complicated for most packages.

> Thanks,
> Adam

-- 
Philip Kaludercic