On Apr 15, 2015 10:07 PM, "François Laupretre" <franc...@php.net> wrote: > > >De : Pierre Joye [mailto:pierre....@gmail.com] > > > > Again, take #3, ext released in and outiside the core will use the external version number everywhere. Like oci, zip and other well managed versions. > > The stupid think like 0.1 since 8 years will use the php version. That is all. > > > > Or am I missing something obvious? > > No, I just didn't understand you were just talking about extensions *not* released outside of the core distrib. > > So, I am adapting my questions :) : > > - When we distribute the same extension code in more than one PHP release, which version do we set for this extension ? Do we set a different version for the same code in each release ? > > - If a new PHP version is released, do we need to change the extension version even if the code was not modified ?
Good extensions synchronize core and external releases. For example, by the time 5.6.8 is released, the codebase matches 1.3.4 for the external release. That will be the version exposed for the core. The problem we have now is core extensions with senseless versions without any external versions. Or mixed codebase, like core is a mix of external and core specific codes which is not in any external releases. That is what we should solve.
