[Pyrex] ANN: Pyrex 0.9.6

Jesus Cea jcea at argo.es
Mon Oct 8 13:21:32 CEST 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greg Ewing wrote:
>> Greg, what are your points to not have a public repository with
>> incremental changes?
> 
> I'm considering it, but I haven't thought through all the
> implications of how it would work.

I think the point is to have a read-only repository to be able to check
your work before you officially do a release.

Something like being able to say something like "the SVN version 931
breaks this code...", or "checking versions, this bug was introduced in
versión 732".

Read-only would be enough, if you keep the repository up-to-date
(ideally, your *actual* version controlled up-to-date code). That is,
publish your current source control system publically as read-only.

- --
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea at argo.es http://www.argo.es/~jcea/ _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea at jabber.org         _/_/    _/_/          _/_/_/_/_/
                               _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCUAwUBRwoSvJlgi5GaxT1NAQLr2AP4mYSlTvHyRjPPafVtw8yId7N0gdXHpKZE
4Z3atGQ+lwCjqeSjMUv82Jurs8ia3jKvjM4h6UCQvLhqnnSJiKH879Y2TK5Hw4dR
3/RI9SobU/ifTZEK+PCyLWuojYhjyrCK2+iz2ZIjIUJ7v+bJDomfpEqr/U1YYIYH
elURao/H3A==
=TmMh
-----END PGP SIGNATURE-----



More information about the Pyrex mailing list