Re: Bleeding edge in elpa

[Aaron Ecay <aaronecay@gmail.com>]

Hi Terry,

2015ko martxoak 9an, "T.F. Torrey"-ek idatzi zuen:
>
> Hello,
>
> Rasmus <rasmus@gmx.us> writes:
>
>> As I think somebody said, the correct "fix" to this problem is more
>> frequent released.  I'm sure Bastien would appreciate help with this.
>> Do you want to volunteer?
>
> If the goal is to have the latest and greatest version of Org available via
> ELPA (for all the reasons some people use ELPA instead of git), there
> are two obvious options:
>
> 1. Org could have a stable release every month or so.
>
> 2. The Org server could be configured to automatically package the
> master version of Org every day, as the maint version is now.
>
> Option 1 is widely regarded as the best choice.  However, it requires a
> lot of actual, repeated human effort.  As Debian repeatedly
> demonstrates, this is very hard to do, even once.  If option 1 could be
> done, it would already be done.
>
> Option 2 would be a one-time (mostly) human effort, and the daily work
> would be automated.

But what would not be automated is the actual human effort that goes into
making a release: writing NEWS and documentation for new features, testing
for regressions, generating the emacs Changelog files, merging changes
from emacs trunk back into to org code base, merging org code into emacs
trunk, ...  Someone still has to do all those things eventually.  Or not,
and the quality of org as a software product suffers.

--
Aaron Ecay