From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Tramp as ELPA package
Date: Sun, 26 Aug 2018 20:04:51 +0200 [thread overview]
Message-ID: <878t4t9f7g.fsf@gmx.de> (raw)
In-Reply-To: <jwvmut9qier.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 26 Aug 2018 11:21:09 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> To the extent that the *-pre aren't distributed IIUC, I'm not sure what
> problem would be caused by simply keeping the version string at "2.4.0"
> instead of "2.4.1-pre".
Between "2.4.0" and "2.4.1", there is half-a-year. Very likely, I would
like to release error fixes in the time between.
And for debugging purposes, it is important whether somebody uses a
Tramp release like "2.4.0", or something taken from a repository, named
"2.4.1-pre". In the latter case, I must be more careful to understand,
which Tramp file versions are used.
>> Maybe we need an intermediate release string as the MELPA packages
>> have: add a time stamp in the Version: header of tramp.el *only* in
>> the Emacs repository, whenever a new version of Tramp shall appear as
>> package, like 2.4.1.pre.20180826. This shouldn't be done
>> automatically, by intention only. An automatic release of Tramp as
>> ELPA package might be too frequent, I fear.
>
> I don't understand: GNU ELPA packages are only created when the
> Version: changes, so it's only as frequent as you choose it to be.
That's the problem. If I keep the release scheme "2.4.0", 2.4.1", ...,
there's a release every half-a-year. I don't want to change this
timing, because it is always a several-days effort for a release. I do
run heavy regression tests prior the release, for example.
But maybe we shall indeed use something like a Tramp ELPA package
release scheme, with something like "2.4.0.1", "2.4.0.2", ..., without
all the effort to make a "real" release as tarball, as it should still
happen.
>> * Several Tramp versions. I maintain several Tramp versions in parallel,
>> currently 2.3.4 and 2.4.1. I'm not confident that 2.4.1 shall be the
>> ELPA package today, because new features will be added here, and it is
>> kind of unstable, therefore. I believe, 2.3.4 would be better suited
>> for all users *not* running Emacs 27.0.50. Users running Emacs 27.0.50
>> do not need Tramp as ELPA package, because it is always synced with
>> the Emacs repository. How do we manage this?
>
> We don't. Org-mode is in the same situation.
>
> All other packages (including Emacs itself, BTW) far only have one
> "active" release, basically.
No. Emacs has the master branch, and the emacs-26 branch. I would call
both "active".
> IIUC the multiple-releases dance is mostly out-of-fashion in these days
> of "DevOps".
I don't understand what you mean with this. (And yes, I know what DevOps
means in general.)
>> * Providing Tramp documentation. IIUC, ELPA packages could contain
>> *.texi and *.info files, but they are not propagated to the
>> users. This shall be enhanced, because new features of Tramp are
>> reflected there.
>
> The .info files are "propagated to the users", but the .texi files
> indeed are currently left unused.
As Tom reminded me, it requires to add a proper "dir" file to the Tramp
ELPA package. Since it would be a core package, I ave no idea where this
file to take from.
> Stefan
Best regrads, Michael.
next prev parent reply other threads:[~2018-08-26 18:04 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 13:24 GNU ELPA package for CC-mode Stefan Monnier
2018-08-19 20:49 ` Alan Mackenzie
2018-08-19 23:45 ` Stefan Monnier
2018-08-20 8:24 ` Jostein Kjønigsen
2018-08-20 14:06 ` Stefan Monnier
2018-08-20 17:58 ` Jostein Kjønigsen
2018-08-21 13:30 ` Stefan Monnier
2018-08-21 16:20 ` Alan Mackenzie
2018-08-23 5:25 ` Stefan Monnier
2018-08-23 21:34 ` Alan Mackenzie
2018-08-23 22:17 ` Stefan Monnier
2018-08-24 8:43 ` Eli Zaretskii
2018-08-24 11:56 ` Michael Albinus
2018-08-24 22:21 ` Stefan Monnier
2018-08-25 8:43 ` Tramp as ELPA package (was: GNU ELPA package for CC-mode) Michael Albinus
2018-08-25 18:04 ` Tramp as ELPA package Stefan Monnier
2018-08-25 21:04 ` Stefan Monnier
2018-08-26 6:39 ` Andreas Schwab
2018-08-26 10:48 ` Michael Albinus
2018-08-26 11:09 ` Michael Albinus
2018-08-26 15:21 ` Stefan Monnier
2018-08-26 18:04 ` Michael Albinus [this message]
2018-08-26 18:27 ` Eli Zaretskii
2018-08-26 18:34 ` Michael Albinus
2018-08-26 19:03 ` Eli Zaretskii
2018-08-27 7:12 ` Michael Albinus
2018-08-27 13:33 ` Stefan Monnier
2018-08-27 13:41 ` Michael Albinus
2018-08-27 13:44 ` Stefan Monnier
2018-08-27 15:22 ` Michael Albinus
2018-08-27 15:09 ` Eli Zaretskii
2018-08-27 15:21 ` Michael Albinus
2018-08-26 15:30 ` Tom Tromey
2018-08-26 16:26 ` Stefan Monnier
2018-08-26 17:46 ` Michael Albinus
2019-04-04 12:41 ` Michael Albinus
2019-04-04 15:48 ` Stefan Monnier
2019-04-04 16:07 ` Michael Albinus
2019-04-05 14:43 ` Michael Albinus
2019-04-05 15:07 ` Dmitry Gutov
2019-04-05 16:19 ` Michael Albinus
2019-04-16 7:53 ` Steinar Bang
2019-04-05 18:14 ` Stephen Leake
2019-04-05 18:20 ` Stephen Leake
2019-04-05 22:18 ` Michael Albinus
2019-04-07 0:17 ` Stephen Leake
2019-04-07 7:41 ` Michael Albinus
2019-04-06 12:42 ` Stefan Monnier
2019-04-08 12:37 ` Michael Albinus
2019-04-08 13:07 ` Stefan Monnier
2019-04-08 13:31 ` Michael Albinus
2019-04-08 16:43 ` Stefan Monnier
2019-05-20 13:05 ` Michael Albinus
2019-06-30 19:20 ` Michael Albinus
2019-04-05 18:55 ` Achim Gratz
2019-04-06 22:25 ` GNU ELPA and package.el (was: Tramp as ELPA package) Stefan Monnier
2019-04-07 7:17 ` GNU ELPA and package.el Achim Gratz
2019-04-07 14:07 ` Stefan Monnier
2019-04-07 17:37 ` Achim Gratz
2019-04-07 20:31 ` Stefan Monnier
2019-04-08 17:55 ` Achim Gratz
2019-04-08 19:01 ` Stefan Monnier
2019-04-08 20:24 ` Achim Gratz
2019-04-09 1:39 ` Stefan Monnier
2018-08-25 19:15 ` GNU ELPA package for CC-mode Clément Pit-Claudel
2018-08-25 20:17 ` Stefan Monnier
2018-08-25 21:17 ` Tom Tromey
2018-08-25 23:28 ` Kyle Andrews
2018-08-24 15:48 ` Stefan Monnier
2018-08-24 19:21 ` Eli Zaretskii
2018-08-24 22:17 ` Stefan Monnier
2018-08-25 7:02 ` Eli Zaretskii
2018-08-25 8:51 ` Alan Mackenzie
2018-08-25 10:15 ` Michael Albinus
2018-08-25 18:07 ` Stefan Monnier
2018-08-25 18:27 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878t4t9f7g.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).