Re: [Repoze-dev] Migration to Github
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? -- Brian Sutherland ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
On 24 March 2011 12:02, Brian Sutherland br...@vanguardistas.net wrote: 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? Looking at e.g. https://github.com/repoze/repoze.vhm, it seems that releases are just given a version-tag, e.g. 1.1. $ git tag -s 1.1 $ git push --tags \malthe ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
-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 Designhttp://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
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2011 10:54 AM, Brian Sutherland wrote: On Tue, Feb 22, 2011 at 09:40:38AM -0500, Tres Seaver wrote: We have chosen to leave dormant projects in SVN for the indefinite future.. Please let us know if there is an existing 'repoze.*' project which you think needs to be migrated: repoze.bitblt is also used and maintained. Now moved to github: https://github.com/repoze/repoze.bitblt Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2Inb8ACgkQ+gerLs4ltQ51VQCeKwRxozI7a243tgQ4vKYUhrly iRgAn1YCmVxdL/IVDf6KvTekm1Dn/bGk =Vda2 -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
On 3/22/11 14:01 , Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2011 09:54 AM, Wichert Akkerman wrote: On 2/22/11 15:40 , Tres Seaver wrote: We have chosen to leave dormant projects in SVN for the indefinite future.. Please let us know if there is an existing 'repoze.*' project which you think needs to be migrated: repoze.filesafe is still actively maintained and used, so it should probably be added to the list. Now moved to github: https://github.com/repoze/repoze.filesafe Is there still a way for me to commit to it now? Wichert. ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2011 09:40 AM, Tres Seaver wrote: These packages are all now moved to github: - [X] repoze.accelerator - [X] repoze.browserid - [X] repoze.catalog - [X] repoze.component - [X] repoze.configuration - [X] repoze.debug - [X] repoze.errorlog - [X] repoze.folder - [X] repoze.lemonade - [X] repoze.lru - [X] repoze.mailin - [X] repoze.profile - [X] repoze.retry - [X] repoze.sendmail - [X] repoze.sphinx.autointerface - [X] repoze.tm2 - [X] repoze.who - [X] repoze.workflow - [X] repoze.zcml - [X] repoze.zodbconn Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2IniIACgkQ+gerLs4ltQ7ULgCfSj1YC1KAevbE649DAqBBCK+2 MesAn3Khl2w9ZSyzm3zar1yvEUrQ27CZ =07SD -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/22/2011 09:02 AM, Wichert Akkerman wrote: On 3/22/11 14:01 , Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2011 09:54 AM, Wichert Akkerman wrote: On 2/22/11 15:40 , Tres Seaver wrote: We have chosen to leave dormant projects in SVN for the indefinite future.. Please let us know if there is an existing 'repoze.*' project which you think needs to be migrated: repoze.filesafe is still actively maintained and used, so it should probably be added to the list. Now moved to github: https://github.com/repoze/repoze.filesafe Is there still a way for me to commit to it now? The general procedure is now like so: - - Fork the repository you are interested in. - - Sign CONTRIBUTORS.txt by adding your name and the date to the bottom. - - Commit and push your fork. - - Issue a pull request back to the original repository. Chris or I will then merge that pull request and add you to the appropriate team, which gives you the right to push to the main repository. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2InwAACgkQ+gerLs4ltQ7gywCfRGPoqrMEhVPI1wcMPkesFVp9 JAUAnRXqBZxhnpQGmBGwE1B7eUMCOF1Q =nhn9 -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
On 22 February 2011 14:40, Tres Seaver tsea...@palladion.com wrote: We have chosen to leave dormant projects in SVN for the indefinite future.. Please let us know if there is an existing 'repoze.*' project which you think needs to be migrated: Please migrate repoze.xmliter. I'm maintaining this for use with plone.app.theming / diazo (xdv). Laurence ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/22/2011 10:13 AM, Laurence Rowe wrote: On 22 February 2011 14:40, Tres Seaver tsea...@palladion.com wrote: We have chosen to leave dormant projects in SVN for the indefinite future.. Please let us know if there is an existing 'repoze.*' project which you think needs to be migrated: Please migrate repoze.xmliter. I'm maintaining this for use with plone.app.theming / diazo (xdv). Done. Please fork, sign COMMITTERS.txt, commit / push, and do a pull request: https://github.com/repoze/repoze.xmliter Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2IttYACgkQ+gerLs4ltQ7bMQCfSy/jqbyIfbTXpOYWI/bvBfE7 p3UAoNtrCreX1mzYiJQ2vZTUzAgELVJA =Zvpy -END PGP SIGNATURE- ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
On 2/22/11 15:40 , Tres Seaver wrote: We have chosen to leave dormant projects in SVN for the indefinite future.. Please let us know if there is an existing 'repoze.*' project which you think needs to be migrated: repoze.filesafe is still actively maintained and used, so it should probably be added to the list. Wichert. ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Migration to Github
On Tue, Feb 22, 2011 at 09:40:38AM -0500, Tres Seaver wrote: We have chosen to leave dormant projects in SVN for the indefinite future.. Please let us know if there is an existing 'repoze.*' project which you think needs to be migrated: repoze.bitblt is also used and maintained. -- Brian Sutherland ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
