Next major roadmap

[soullivaneuh]

According to #337 (comment), here is a roadmap for the next 2.0 major of this bundle:

• Bump PHP support to 7.1 → [WIP] [2.x] Version bumps #366
• Introduce PHP7 type-hinting -> Dependencies upgrade #379
• Move to psr-4 new directory structure (src and tests) → [2.x] PSR-4 friendly structure #365
• Bump PHPUnit support to v6 -> Dependencies upgrade #379
• Bump Symfony support to v3.4. As it's the next LTS, it would make sense
• Bump nelmio/alice support to v3 => nelmio/alice v3 #268 and Nelmio Alice v3 upgrade #337
• Bump Twig support to v2 -> Dependencies upgrade #379
• Bump jackalope/jackalope-doctrine-dbal support to v1.3 -> Dependencies upgrade #379
• Bump brianium/paratest to v1 -> Dependencies upgrade #379
• Check and bump other dependencies to latest -> Dependencies upgrade #379

This are ideas I got right know. Feel free to comment if you want to add/modify/remove any of them.

Also, feel free to participate to this next major. 👍

[alexislefebvre]

Note that there is another roadmap in #332.

[soullivaneuh]

Yeah I saw it later, but not quite the same.

Thanks for linking it. 👍

[Jean85]

I would add supporting Symfony as ^3.0||^4.0 which would help most people with no big problems on our side. If the maintainers are 👍 with this issue, I would ask them to open a branch for this, I would gladly help.

[soullivaneuh]

@Jean85 ^3.4 || ^4.0 is preferable IMHO, we don't have to support EOL version of Symfony on the next major.

[Jean85]

I know, but since we're talking about Symfony, we could impact a great deal of upgrade issues, since it will drag any Symfony component with it. I would prefer to bump it upwards from ^3.0 only if needed; due to their nice BC promise we could have no issues with that.

[soullivaneuh]

due to their nice BC promise we could have no issues with that.

Well, we generally have to make BC trick on library. For example, if we want to use a method introduce in v3.2, we have to make the usage conditional with support of ^3.0.

As you said, there is a BC promise, but for end user. And to complete your sentence, the end user may upgrade to Symfony 3.4 without any issue. 😉

[Jean85]

I've opened #359 to start development of this issue. Obviously a lot of tests are failing, but it's a starting point...

Can we add a tool for automatic CS fixing in this roadmap?

[soullivaneuh]

Can we add a tool for automatic CS fixing in this roadmap?

@Jean85 Funny to ask, I made one recently: https://flintci.io

May we try it? 😄

[Jean85]

Eheh 😄 we should ask @lsmith77 ...
BTW, can you update the checklist, since #365 got merged?

[lsmith77]

I like automation and I do not have any strong preferences .. I used https://styleci.io in the past and liked it. but I am fine trying out something new.

[soullivaneuh]

@lsmith77 The only lack of StyleCI for me is the absence of cli fix possibilities. This is why I made a bridge but this one is not compatible with php-cs-fixer v2 anymore. I'll try a PR for that. 👍

BTW, can you update the checklist, since #365 got merged?

@Jean85 Sorry but I don't see which point this PR solve. 😕

[alexislefebvre]

I think that the biggest challenge will be the compatibility with Alice, work has begun in #297, #321 and #337 and I have no idea about a solution. Help is welcome!

[Jean85]

Before solving those, IMHO we should get the build to green in #366, so we can define the range of deps that we want/are able to support...

@soullivaneuh, @alexislefebvre are you able to help me?

[alexislefebvre]

I think that we should add a note about the 2.x and master in order to explain that new features should go to 2.x. And that this version is still under development.

nelmio/alice use something like this:

2.x is in maintenance mode: PRs are accepted, but no active development is done on it by the maintainers any longer.

We'll also need to explain all the BC changes in order to ease the upgrade to 2.x.

[soullivaneuh]

This issue is completed.