Re: Bug: Please supply stable releases on ELPA or MELPA Stable [8.3.4 (8.3.4-dist @ /usr/local/share/emacs/25.1.50/site-lisp/org-mode/)]

[Nicolas Goaziou <mail@nicolasgoaziou.fr>]

Hello,

Achim Gratz <Stromeko@nexgo.de> writes:

> No, we shouldn't.  It's either automatic or a release, it can't be
> both.

I can't see why. We already "release" automatically new packages.

> Also, the releases are distinct from the ELPA packages and you seem to
> mix up the two.  They are not the same thing.

By release, I mean the act of releasing a new version, not the type of
output (tar.gz, ELPA package). 

In any case, I think it is confusing to have ELPA packages differ from
source releases. Installing through ELPA could be made equivalent to
installing latest stable sources, i.e., both output could be generated
at the same time.

It means that bugfix releases should happen more often and ELPA packages
less often.

>> 1. org-YYYYMMDD could be renamed org-MAJOR-MINOR-BUGFIX# where MAJOR
>>    MINOR are never modified automatically, and BUGFIX# is (1+ last
>>    BUGFIX#).
>
> Org's ELPA package has its own versioning scheme and unless package.el
> grows some functionality to sanely deal with discontinuities in
> versioning, we need to stick to it.

It may be. Not providing org-YYYYMMDD versions anymore could be a step
in the direction of replacing them.

In the worst scenario, we can keep them as packages, and still provide
org-X.Y.Z alongside.

>> 2. Conditions to make a new automated release ought to change. We could
>>    wait for a full "idle" week after a commit before releasing (IOW,
>>    wait for one week after a commit but every new commit during that
>>    period resets the counter). "next Monday" rule has bitten us already.
>>    The new rule is not perfect either, but is more secure. If one full
>>    week is too long, we may reduce it to 4 days.
>
> Again, if you talk about releases, the way to do that is to tag what
> should be released, preferrably sign the tag as well.  Whether you roll
> the release automatically or script up somthing that picks up new tags
> and does it for you is a separate issue.

Per above, the script should also generate a new ELPA package.

> BTW, if the Monday ELPA package is bad you can always trigger another
> release to ELPA manually

How?

> and don't need to wait for next Monday to have cron run the release
> script.

This is the opposite of what I'd like to see. Release script should be
run less frequently, not more.

Regards,

-- 
Nicolas Goaziou