[DRE-maint] Bug#972605: jekyll: Please update to new 4.x branch
calumlikesapplepie at gmail.com
calumlikesapplepie at gmail.com
Wed Oct 21 18:15:49 BST 2020
On Wed, 2020-10-21 at 15:12 +0200, Daniel Leidert wrote:
> Am Dienstag, den 20.10.2020, 23:33 -0400 schrieb Calum McConnell:
>
> > Jekyll upstream has been concentrating on a new 4.x release branch
> > for the
> > past year. It provides a significant set of new features that I
> > use, and it
> > would be great if it could be included in debian.
> >
> > I assume you know all of that already, since 3.9 released after
> > 4.0, but I
> > was wondering what the rationale was for sticking with the 3.x
> > branch.
>
> It is very stable and well tested. Also not all plugins had been
> ported to
> Jekyll 4 at the beginning of the year (not sure about the current
> state).
> Further it would make backporting to current stable a lot more
> complicated.
> I'm not aware of any ground-breaking changes. What features are you
> referring to?
Its not exactly ground-breaking (I might have exaggerated
'significant'), but the caching system is really handy. I like to
iterate rapidly, and a cache is really, really helpful for that: it
halves build times.
Also, there a bunch of little changes, such as relative-url, that I
appreciate. The sort of changes that a user might try to use, and then
be confused as to why they don't work.
The biggest reason, though, is that 3.9 is like Python 2.7: it's
probably the last release of the series. According to rubygems, 3.9.0
has a third the downloads of 4.1.1, and a sixth of 4.0.0: its clear
people are moving up to the next version, and will eventually need to
do so if they want to keep getting support for plugins. I believe
there are already some 4.0-only plugins.
In short, we probably ought to have it in Bullseye before we release.
> The 4.x series will be uploaded to experimental eventually. But I'm
> hesitant to upload it to unstable just now.
Okay: fair enough. But the 4.0 branch is about a year old, and I
haven't really felt any major issues with it. I think most plugins
have upgraded by now:
Thanks for considering. Let's keep this bug open, so that you don't get
another person reporting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20201021/f77963f0/attachment.sig>
More information about the Pkg-ruby-extras-maintainers
mailing list