While still working on #1704734: [master] Libraries API 8.x-3.x, let's cut an 8.x-3.0 stable release. It's stable already. There haven't been any commits to library module's 8.x branch in almost a year, and there are very few bugs reported against it.

Comments

douggreen created an issue. See original summary.

douggreen’s picture

douggreen CreditAttribution: douggreen at Appnovation for Pfizer, Inc. commented
Issue summary: View changes
douggreen’s picture

douggreen CreditAttribution: douggreen at Appnovation for Pfizer, Inc. commented
Title: Tag an 8.x-1.0 release » Tag an 8.x-3.0 release
Issue summary: View changes
tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
CreditAttribution: tstoeckler as a volunteer commented
Status: Reviewed & tested by the community » Postponed

I just tagged an 8.x-3.0-alpha1.

I am not really happy with the current state of the module, so I am actually not comfortable with creating a stable release. We did have some quite ambitious plans for this module at some point, unfortunately we never achieved them. But even if we decrease the scope of the module I'm not happy creating a stable release with all the stuff that is alreay in there that is broken.

So I am going to mark this issue postponed for now. If any of the other maintainers feel differently I certainly don't want to hold anyone up.

douggreen’s picture

douggreen CreditAttribution: douggreen at Appnovation for Pfizer, Inc. commented

fair enough, I should of just asked for a tagged release.

sun’s picture

sun
Primary language German
Location Karlsruhe
CreditAttribution: sun at netzstrategen commented

Libraries API is pretty important for D8 sites and installation profiles.

If possible in some way, we should release a tagged release of 8.x-2.x in some stable-ish form to allow the whole (Drupal) project and community to make progress on many other fronts. The comments on this issue sound like that release could even be a 8.x-2.0.0 after quickly cleaning up some experiments?

All code targeting a major rewrite / refactoring should be postponed to a new major 3.x at this point in time of the Drupal Core release cycle.

tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
CreditAttribution: tstoeckler as a volunteer commented

So the problem is that the asset system got drastically revamped between D7 and D8 so a straight port is simply not possible. That's not just in terms of removed/revamped APIs, but conceptually Libraries API cannot work as it did in D7, as it relied on the runtime adding of assets (drupal_add_js/css()) which got completely removed (i.e. not just replaced with an OO-version). If someone has concrete plans/ideas or even code for a less ambitious version of a D8 Libraries API than what is currently in 8.x-3.x I'm fine with going for a 8.x-2.x, but so far that simply doesn't exist.

Chris Matthews’s picture

Chris Matthews CreditAttribution: Chris Matthews as a volunteer commented
Related issues: +#1704734: [master] Libraries API 8.x-3.x
Chris Matthews’s picture

Chris Matthews CreditAttribution: Chris Matthews as a volunteer commented

Opened issue #3039570: Plan for a "less ambitious" version of D8 Libraries API

xeM8VfDh’s picture

xeM8VfDh CreditAttribution: xeM8VfDh commented

Is this still postponed? D8 has been out for a long time now, as has this module. Can we get a stable release tag?