[Tracker-discuss] Getting Started

[Erik Forsberg]

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

"Paul Dubois" <pfdubois at gmail.com> writes:

> 1. I strongly suggest the vendor-branch method I mentioned before. That
> would mean that in this case you create a 'vendor' branch consisting of the
> version of Roundup that you modified to make the prototype. Then branch it
> to 'ours'. Submit the prototype as a change to 'ours'. Then we can start
> modifying it as needed.

I'm with you on this one. I use vendor branches extensively at work,
and it's a very good way of managing code in this kind of project. 

One of my colleagues has written a tool for automating this kind of
task that is superiour to svn_load_dirs.pl (which only does half the
job). Here's a mailing list post with source code:

http://subversion.tigris.org/servlets/ReadMsg?listName=users&msgNo=56591

> 2. On the existing metatracker I noted a couple of bugs for the data
> migration. Are these something we need to work on?

Yes. 

> 3. Perhaps everybody but me knows, but what method of deployment are we
> going to use? I have only done the stand-alone server running behind Apache
> with a proxy-pass, and I don't know the pros and cons of the various
> approaches.

This needs to be discussed. I don't know what's best practice for
large installations of roundup. I'm running the demo tracker
(http://efod.se/python-tracker) and the meta tracker
(http://efod.se/ptt) via mod_python.

I guess Richard and/or the roundup-users list might have something to
say here.

\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFFSMyjrJurFAusidkRAux6AKCDLjFRUKYrWz9deg7GXMKVwgoT/QCfXYUW
2xO3Yi1L6lxHt8qT7N7lmgI=
=ygib
-----END PGP SIGNATURE-----