On Jan 16, 2015 7:03 AM, "Pierre Joye" <pierre....@gmail.com> wrote: > > > On Jan 15, 2015 10:24 PM, "Benjamin Eberlei" <kont...@beberlei.de> wrote: > > > > On Thu, Jan 15, 2015 at 4:11 PM, Jan Ehrhardt <php...@ehrhardt.nl> wrote: > > > > > Benjamin Eberlei in php.internals (Thu, 15 Jan 2015 15:53:43 +0100): > > > >Not sure how that helps, since you would tag versions anyways using > > > semver, > > > >so if there is a master vs next/phpng branch, then they might still result > > > >in two tags v1.0 and v2.0 and there is no way to automatically resolve > > > this. > > > > > > The branch name convention was meant for those developers that want to > > > maintain the same version for both PHP7 and PHP5.x. In thoese cases > > > there is no difference in version tags. Just a git checkout -b phpng if > > > you want the PHP7 branch. > > > > > > > Oh ok my bad. I was under the impression this was for distro/packaging > > reasons or something > > as a convention. > > Well there is a concern about packaging using this method. As of now it is not possible to package them. > > I tend to prefer separate files and add the right source at configure time. It is then easier to keep fixes, features, etc. in sync. > > However both solutions may work, if we decide to go for one or another solution. We can add support for the packaging/install in pickle and the website. > > It is also important to note that I would like to push the usage of install from git/other VCS in the near term, using pickle, and use the website only for the meta info but not (or much less) for hosting the releases.
Also using branches may be an issue too with semantic versions, for the version names, using composer-like tags/branch fetch.
