Added a BC note

[Nyholm]

It should be more clear what our BC is. With this BC promise we can.

• Change the order of our strategies and add strategies in any order
• Change the order/priority of classes in CommonClassesStrategy

The consequence is that you can never be sure what client that is going to be found but you can be sure that updating a minor version will not result in that a client is not found any more.

Related to #48

[sagikazarmark]

I would rather say "we promise to support/not remove the following classes: [list]".

[Nyholm]

I don't want to make a list because it will be harder to maintain (especially if we move this to the documentation repo). But the formulation could be improved.

[sagikazarmark]

Shouldn't we rather place this in the documentation?

[Nyholm]

Maybe it should be placed in the documentation repo. I just figured, if you are about to update versions you are most probable to go to packagist, github and then to our documentation page.

In one way it makes sense to have the BC promise close to the changelog and upgrade docs. But it do also make a lot of sense to have the BC promise next to all our other documentation.

Maybe we should create a full page in the docs about our general BC promise and all our special ones (like this and possible also for HTTPlugBundle).

[sagikazarmark]

Sounds like a good idea to me.

Tobias Nyholm notifications@github.com ezt írta (2016. július 16.,
szombat):

Maybe it should be placed in the documentation repo. I just figured, if
you are about to update versions you are most probable to go to packagist,
github and then to our documentation page.

In one way it makes sense to have the BC promise close to the changelog
and upgrade docs. But it do also make a lot of sense to have the BC promise
next to all our other documentation.

Maybe we should create a full page in the docs about our general BC
promise and all our special ones (like this and possible also for
HTTPlugBundle).

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#77 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABK2kOVM48aEkHJoYikCgHd8T5dMYZ3uks5qWLBbgaJpZM4JN-0s
.