Zope2 git mirror not updating?
I noticed that the Zope2 git mirror does not appear to be updating. Looking at https://github.com/zopefoundation/Zope/commits/2.13 it doesn't have any commits after November 15, while subversion has more recent commits from Hanno and Maurits. Did an updating process break? Or did development switch to github but the subversion repository was not made readonly? Wichert.
On Jan 11, 2013, at 14:07 , Wichert Akkerman <wichert@wiggy.net> wrote:
I noticed that the Zope2 git mirror does not appear to be updating. Looking at https://github.com/zopefoundation/Zope/commits/2.13 it doesn't have any commits after November 15, while subversion has more recent commits from Hanno and Maurits. Did an updating process break? Or did development switch to github but the subversion repository was not made readonly?
I had already mentioned in a different thread that the Zope and all Products.* packages you see on GitHub are not final migrations, just test migrations. Until a package is clearly marked as migrated in SVN (such as all packages Jim and Tres migrated) the migration is not final and all changes should still be checked into svn.zope.org. jens
On Jan 11, 2013, at 14:10 , Jens Vagelpohl <jens@dataflake.org> wrote:
On Jan 11, 2013, at 14:07 , Wichert Akkerman <wichert@wiggy.net> wrote:
I noticed that the Zope2 git mirror does not appear to be updating. Looking at https://github.com/zopefoundation/Zope/commits/2.13 it doesn't have any commits after November 15, while subversion has more recent commits from Hanno and Maurits. Did an updating process break? Or did development switch to github but the subversion repository was not made readonly?
I had already mentioned in a different thread that the Zope and all Products.* packages you see on GitHub are not final migrations, just test migrations. Until a package is clearly marked as migrated in SVN (such as all packages Jim and Tres migrated) the migration is not final and all changes should still be checked into svn.zope.org.
Ok, noted. Perhaps it would make sense to not give write access on github for repositories that are not officially migrated to prevent confusion? I'm afraid I committed something on both github and svn.zope.org now since I initially thought github was the thing to use. Wichert.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/11/2013 08:10 AM, Jens Vagelpohl wrote:
On Jan 11, 2013, at 14:07 , Wichert Akkerman <wichert@wiggy.net> wrote:
I noticed that the Zope2 git mirror does not appear to be updating. Looking at https://github.com/zopefoundation/Zope/commits/2.13 it doesn't have any commits after November 15, while subversion has more recent commits from Hanno and Maurits. Did an updating process break? Or did development switch to github but the subversion repository was not made readonly?
I had already mentioned in a different thread that the Zope and all Products.* packages you see on GitHub are not final migrations, just test migrations. Until a package is clearly marked as migrated in SVN (such as all packages Jim and Tres migrated) the migration is not final and all changes should still be checked into svn.zope.org.
AFAICT, the git.zope.org mirroring process is not functioning. E.g., the 'py3' branch of ZODB is not there, lots of repositories are mssing altogether, etc. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlEyOjoACgkQ+gerLs4ltQ43zACfSKI/4kJt8qI7e88XHsp8FMug UmEAoLAME3K4UGEEC3s2Lam4srgZA68k =R8VZ -----END PGP SIGNATURE-----
participants (3)
-
Jens Vagelpohl -
Tres Seaver -
Wichert Akkerman