PEAR 1.10

Hi all,


> The work we have to do is 
> - create 1.10 branch
> - find out which patches can go into 1.10.0
> - cherry-pick them from master
> 
> master is too unstable for a no-dedicated-maintainer release.
> The gpg validation for example is not ready for release.

I've re-migrated pear-core from SVN to git, preserving all the tags
this time and using correct authorship information.

So we've got a 1.9 branch now that the last 1.9.5 release was based
off, and master that contains all commits to date.

Unfortunately, version 1.9.2 was already off master by some dozen
commits. Fixes were ported from and to master in the subsequent 1.9.x
releases, but they were never in sync.

What we can do now:

- Port important fixes into the 1.9 branch, knowing that it's stable
  because the code lasted the last 4 years

or

- Stabilize current master with all the new features in it, making it
  ready as 1.10 release

or 

- Find a point in time master was stable enough before all the github
  merges came in, make it the 1.10 branch and cherry-pick stable
  fixes into it.

Ideas?

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iEYEARECAAYFAlN6cHcACgkQFMhaCCTq+CM8cACgs7IxmHhGiM6x6CBk6G8O+Ezt
3kMAoIbHmt1twO//QqCiDmZzatRYwE5x
=pEpe
-----END PGP SIGNATURE-----