> I'd like to get involved in testing prior to releases, and am > wondering > if there are any release test documents I could review.
Sure! Start with TESTING-README in the branch root. I'd suggest running the functional tests against your postgres database, something that Bitten doesn't currently do. To try that, edit the initenv call trac/tests/functional/testenv.py:64 to provide the correct db uri, and run 'python trac/tests/functional/__init__.py' (if you get pythonpath issues, just add pwd to it). If you intend to do coverage reports, pay special attention to the notes in the TESTING-README. Last I checked, all those tests would pass on Python 2.4 and above on various Linux distros, OS X Leopard, and Windows XP/Server 2003. I'd be glad to help on IRC (ideally during PST evenings). Let me know. > I'm running a multi project trac Does this mean the 0.12 multi repo, or just with a PARENT_DIR? > I'd also like to receive svn commit emails so I can be aware of what > changes are happening. If someone can help guide me in getting > started > with helping out, that would be great. I don't get those myself. If you use RSS, I'd suggest subscribing to the Timeline RSS feed. Tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
