http://forum.ztracker.org/feed_rss?section=systemzForum is a SQL-Based Message Board Based in Zope2010-09-07 07:20:00zForum Internal RSS Aggregatorhttp://blogs.law.harvard.edu/tech/rsshttp://forum.ztracker.org/view_topic?topic_id=18May 12, 2007 - The latest version of zTracker has been released, the main addition is the ability to add "due dates" to tickets, the view ticket page and the search results pages have been changed and the view ticket page has been updated to take the due date fields, from the changes.txt file: zTracker 1.0 (Rev 3) ==================== - Released May 12 - Color cue for error messages had wrong CSS class defined - Added "deadline" (due_date) for tickets, this will eventually help fine-tune ticket reports - Subscription/Unsubscription change button in "view ticket" page has a more descriptive message - Small changes to "view tickets" (view_tickets.pt) template added "assigned to" and "due_date" columns If you are installing abrand new nstance of zTracker please visit the general installation topic in this forum, if you are upgrading from a previous version of zTracker, please visit the upgrading zTracker topic in this forum. -- sbhttp://forum.ztracker.org/view_topic?topic_id=182007-05-12 10:36:00http://forum.ztracker.org/view_topic?topic_id=16zTracker has released its second revision, this version fixes a potentially showstopper in the system administration section that would prevent from saving project properties, also several other bugs and enhancements have been applied, from the changes.txt: zTracker 1.0 (Rev 2) ==================== - Released April 25, 2007 - Bugfix #7 - Allow exclusion of closed tickets on view_tickets page (quick view) - Bugfix #9 - Added favicon.ico - Bugfix #22 - Reduce boxed area for ticket response section - Bugfix #29 - Changed JS variables in edit project page (admin section), IE6 apparently does not like JS variable names to have the same name as an element's id. - (Radically) changed the way updates are performed, there is no longer a "zt_upgrades" table in the database, since that would imply having to update the table itself on each product update, which defeats the purpose of "update-through-the-web" approach, the zTracker class now provides its own internal mechanism for updating the SQL database. - Added "install.txt" (very basic steps) in the main zTracker directory If you already have zTracker installed, make a backup of your "acl_users", replace the product with the new copy and visit the main index_html page that will guide you to the system upgrade process. If you are new to zTracker, please visit the appropriate forum for detailed instructions on how to install zTracker. -- sbhttp://forum.ztracker.org/view_topic?topic_id=162007-04-25 13:44:00http://forum.ztracker.org/view_topic?topic_id=6The process for upgrading zTracker has learned from the mistakes of the zForum product. Rather than ask the user to run a series of update files, now zTracker will "detect" what version of zTracker does the user have, and what version of zTracker the user is trying to upgrade to, and apply the appropriate SQL changes automatically. When a newer version of zTracker is out, here are the general steps to follow and also a couple of tips to ensure a proper system upgrade: 1. Make a backup copy of your current (old) zTracker 2. Remove the zTracker folder entirely from the $INSTANCE_HOME/Products directory 3. Untar the new zTracker version (zTracker-1.x.x.tgz) into your $INSTANCE_HOME/Products directory 4. Restart Zope 5. Manage the Zope site and create a new zTracker instance 6. [TIP] At this point you may copy both "acl_users" and "MailHost" and maybe your database connection object from your BACKUP into your newly created instance, to preserve the original default values 7. Visit the main zTracker index_html page using your web browser. 8. At this point the system will determine the necessary steps to update your zTracker instance (You'll have to have an administrative account for this). Some notes or suggestions: You may also write down your original database connection string and your mailhost settings before you add the new zTracker instance so you'll have these values available to you when you are creating (Adding the Product) into your ZODB, also, if you are using LocalFS for attachment repository, you may also have that value ready prior to create your new instance. Any questions or comments please discuss them in this thread.. -- sbhttp://forum.ztracker.org/view_topic?topic_id=62007-04-12 17:10:00http://forum.ztracker.org/view_topic?topic_id=5Here are the requirements for a successful installation of zTracker Prerequisites [Link] - Zope 2.7+ (Tested on Zope 2.9.2) (There is currently no port to Zope 3, however plans for its implementation is underway). [Link] - CookieCrumbler (For form-based authentication) [Link] - Python bindings for MySQL (MySQLdb and ZMySQLDA) (Tested on 1.2.0) [Link] - Python 2.3+ (Tested on Python 2.4.2) [Link] - LocalFS Product (Optional, to handle attachments in the filesystem) Installation - Create a MySQL DB to contain the zTracker tables (all the tables in zTracker are named with the prefix "zt_" which makes it suitable to use with an existing database if you can't create a brand new one for whatever other reasons. - Untar zTracker-1.0.x.tgz in your $INSTANCE_DIR/Products - from $INSTANCE_DIR/Products, cd to the "doc" folder "cd doc" - in the doc folder locate the file ztracker_schema.sql - import the database schema in your mysql database, for example, in linux, assuming the database is called "ztracker_db", the command to import would be something like this: mysql -u user -p ztracker_db < ztracker_schema.sql, or you can use any tools that allow to import a SQL schema into a MySQL DB. - Restart Zope (if you have not done it yet) - Add a zTracker instancehttp://forum.ztracker.org/view_topic?topic_id=52007-04-12 14:35:00http://forum.ztracker.org/view_topic?topic_id=1As some of you may already know, zTracker is an intuitive, easy to use bug and tracking system aiming in the management of software projects. However it can also be used to manage virtually any kind of project where a timeline and a group-effort of people is in order. The "official" description (from zope.org) is: "zTracker is a multi-project issue and bug tracking system for the ZOPE framework, zTracker uses a SQL database for data storage and it aims to be the de-facto bug tracking system for zope applications. zTracker was coded entirely in Python and uses ZPT (Page Templates) for its templating system. This system has recently came out from its BETA testing and it is now recommended to deploy it in a production environment". Some zTracker "trivia": zTracker was created by "speedbird" (me) the same author of zForum, I am a Systems Engineer from Sonora, Mexico that has lived and worked in the U.S. for several years now, currently residing in Las Vegas NV. zTracker Uses SQL for project/ticket back-end, currently MySQL is supported, but I am very close to have Postgres enabled too, (if I can just have these fulltext index searches right... ) zTracker was coded (obviously) in Python, using ZPT (Zope Page Templates) for the UI - All the code was written using the VIM (gvim) text editor, on a MacBook Core Duo, 2Ghz, 1.5Mb RAM, using Parallels and Fusion to host Zope/MySQL, Developed originally in Zope 2.9.5 and MySQL 5.0 on a CentOS 4.4 Virtual Machine. zTracker requires CookieCrumbler, ZMySQLDA, (LocalFS might be required in future releases, to handle file attachments) zTracker was written in my spare time in a period of about 3 months A "commercial" release will follow, which will be provided as a hosting service, both versions (open source, commercial) will be compatible with the commercial version providing additional features. http://forum.ztracker.org/view_topic?topic_id=12007-04-12 11:07:00