Use the currently stable version of Assetic [#1812172]

In #1784774: Remove Assetic component from core, I wrongly advocated the use of Assetic 1.1 which is not currently stable. I asked Kris Wallsmith, the lead dev for Assetic which version we should use and he said to use 1.0 since it's stable and I agree. I typically don't projects with non-stable modules or libraries. Even if the library seems to be nearing stability.

With this issue we should replace the 1.1-alpha version with 1.0 of Assetic.

https://twitter.com/kriswallsmith/status/256918677952290817

Comments

Comment #1

webchick

she/they

English

Vancouver 🇨🇦

commented 14 October 2012 at 03:19

Is there a reason why? Drupal 8 isn't set to ship until September 2013. By then, I imagine 1.0 will be old news.

Comment #2

cosmicdreams commented 14 October 2012 at 03:25

I agree that 1.1 *might* be ready by that time. But I asked the lead developer of Assetic and he recommended that we use 1.0. That's my sole reason why.

He might know that there are still large-ish problems with 1.1 and we'd make more progress implementing on top of what 1.0 has to offer first. The evolve our code when 1.1 becomes solid.

That sounds right to me, because we can iterate off of Assetic's code. I suspect there won't be a large change between 1.0 and 1.1. And if we get really lucky. Maybe Kris will have some time to help us along and help build in support for his libraries into a CMS that many many websites will use in the future.

Comment #3

robloach

he/him

commented 16 October 2012 at 18:36

Issue tags:

+Assetic

This isn't too large of a priority as we're still working on getting it integrated. Let's roll with 1.1 for now and if we run into any stability issues, we'll roll back to 1.0. Making a patch for this is easy. CHANGELOG-1.1.md outlines what's new.

We should keep from pinging Kris on this for a while until things have cooled down on his end.