Release Tasks

[dbu]

• Depend on friendsofsymfony/http-cache: 1.* and remove the @dev
• Add a CHANGELOG.md file saying that this is the initial release
• Update todo in Resources/doc/overview.rst
• Deprecate LiipCacheControlBundle in favor of this, and provide a gist or something how to migrate from LiipCacheControlBundle help how to migrate to the FOSHttpCacheBundle liip/LiipCacheControlBundle#45
• PR on http://symfony.com/doc/current/cookbook/cache/varnish.html to advertise this bundle ;-) and maybe even http://symfony.com/doc/current/book/http_cache.html

[stof]

instead of a gist, I think the migration should be documented in the doc of the LiipCacheControlBundle directly

[dbu]

yeah you are right. maybe even the first thing in the README to make it
clear where its going.

[ddeboer]

Also, @dbu, can you change the LiipCacheControlBundle repo description to note it’s deprecated? I’ve already done so for the Driebit one. The repo description is what people see when browsing packages on Packagist.

[dbu]

good point, done.

[ddeboer]

It seems Packagist now has the option to abandon a package, which gives an even clearer warning to users. Not sure whether you’re ready to do this for the Liip package, but I marked the Driebit one abandoned.

[dbu]

@lsmith77 is the only packagist maintainer of liip cache control bundle. can you please mark the bundle as abandoned?

@ddeboer on branch alias: there is only one alias possible, as you alias the master branch to something. i would say we alias master as 1.1-dev and start a 1.0 branch if there are bugfixes to do. once we feel the need for BC breaks, we should release a last 1.x version and then alias master to 2.0-dev and start working on that. lets try to have as few parallel branches to maintain as possible ;-)

[ddeboer]

@dbu Good point, let's keep our branching as simple as possible. Because of semver, we probably need to maintain at least two branches, new unstable (major) and current stable (minor), but we can limit the latter to bugfixes only. As long as we introduce new features, even BC ones, into the new unstable branch, things won't get out of hand. We'll see. :)

[lsmith77]

done

[ddeboer]

PR to Symfony cookbook is up at symfony/symfony-docs#4175.