-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/24/2011 07:02 AM, Brian Sutherland wrote: > On Tue, Feb 22, 2011 at 09:40:38AM -0500, Tres Seaver wrote: >> After working with git / Github on the Pylons project, we have decided >> to move the "active" / "supported" repoze.* projects over to Github, >> under a new organization: >> >> https://github.com/repoze > > I'd like to make a new release of repoze.bitblt (when my pull request is > accepted). Is there any documentation anywhere about how releases should > be tagged/created within the Repoze github repository?
I have merged the pull request, and added you ('jinty') to a new team which has push rights to the repoze.bitblt repository. We haven't documented the release model because "nobody but us chickens" has been making releases. Essentially, we are just making simple tags in git for a release before pushing the tarball to the cheeseshop. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2LQeQACgkQ+gerLs4ltQ64TACg1HuLO+iUXhwUN+/lwh9zDCCu 3TsAoMcBVal18HnW/EIiDkCmxbnuoUG6 =FUFF -----END PGP SIGNATURE----- _______________________________________________ Repoze-dev mailing list Repozefirstname.lastname@example.org http://lists.repoze.org/listinfo/repoze-dev