Jacob Santos » Trac

WordPress Trac Versions

Jacob Santos — Sat, 19 Jul 2008 22:52:08 +0000

The current WordPress Trac has versions 2.7, 2.8, and 2.9 milestones. Version 2.7 is the current trunk or current version. Version 2.8 will hold the tickets for what will be completed for 2.8. The 2.9 milestone currently holds all of the tickets that will try to be completed in a later date.

The plan at least is to move tickets from 2.9, when 2.7 is released, to 2.8 that the core team wants to release in that version. I’m guessing that next year will see the release of 2.9, 2.10, and probably 2.11. It will be somewhat difficult to get past that 2.9 doesn’t mean 2.9, but 2.09, so that is kind of messed up, but have to wait until next year to find out if that will be the case.

Who knows work might start on Version 3.0 with emphasis on BackPress.

Possibly Related Posts:

Trac 0.11 Looking Good

santosj — Wed, 14 Mar 2007 15:13:39 +0000

I think I am going to try to use Trac again when version 0.11 comes out. I already planned to pass over 0.10 and by the time 0.11 comes out, it should support MySQL well enough to have a live site using it. It should also be very easy to install since some of the more difficult packages that are required have been removed.

I’m still kind of planning on building my own tracker package for DragonU.net and AbsidonGames.com site. It should look a lot like Trac, but I will still like to use it for other projects that need its support. Also, I’ll need something in the mean time while I develop my own solution. Well, the only reason to develop my own is that Trac is somewhat unreliable, but hopefully that will change (and it will be easier to change the template) when this version comes out.

I kind of do plan on learning Python, so it would be nice to tear Trac apart to better learn Python also. Kind of hack together plugins and try to implement features that haven’t been already. Well, by that time, Trac will probably be out.

Still think Trac 0.11 is about two months away to say the least. Bug reports don’t say much when it is still in alpha. Trac 0.10 is stablizing quite well, so by which time Trac does reach the final 1.0 release, it will be stable and full featured product. Something to put Python the map and make people want Python support.

Also think that with the easier install, it won’t be that difficult for Dreamhost to have a one click or at least support it.

Possibly Related Posts:

Switching Back to Trac

santosj — Wed, 04 Oct 2006 16:06:47 +0000

I think I’ll take a look at Trac again once 0.11 comes out. The features seem good enough that it would be somewhat easier to install and removes a really difficult install from the requirements.

I’m happy that 0.10 is out, so the real work can go ahead. However, I’m a little disappointed that the features they are working on are architecture and not better wiki and ticket features. After I suppose they get the back end done, they can start working on the features that people want to see.

The problem is that I don’t know the language and would rather like to see a stable PHP package like Trac. MediaWiki and Mantis bundled could get the job done, but heavy amount of development would be needed to get Mantis and MediaWiki working together in sync and with the same amount of features that Trac has. Plus, the missing Subversion and repository features wouldn’t make it all that impressive.

Possibly Related Posts:

Trac 0.10

santosj — Mon, 29 May 2006 13:02:14 +0000

It seems that daily the amount of bugs keeps decreasing. I’m still not ready to try it out and I won’t be until it is officially released. It appears so far to kick ass, but I won’t know until I use it to know for sure.

I’m really, only excited about this version for the InterWiki and InterTrac support for referencing other wikis to get rid of some of the start Trac Wiki Pages without completely removing them. I’m actually waiting for Trac 0.11 because it removes the clearsilver dependency allowing at least to remove the need to have python installed on the home directory.

Come to think of it, perhaps it won’t since you still need to reference the other python packages to it so it could be a good idea to have it in case it would break the other packages. I don’t think it will, since you could just add the library where the other python packages that Trac is depended on to the list of where Trac looks.

It removes a great deal of hardship and complexity of installing Trac. Oh, Trac 0.10 is also including MySQL support so that you won’t need to depend on SQLite anymore. I like SQLite, don’t get me wrong, but it has been the cause of some conflicts in running a stable Trac environment.

Possibly Related Posts:

Trac 0.10 Critique

santosj — Wed, 08 Mar 2006 05:37:27 +0000

I was looking at what Trac 0.10 could do and the progress of its development. I was happy with its feature set, I was kind of disappointed in its progress. It is moving as fast as my game engine development or a little bit faster. That said, 0.10 will include a lot of cool features that is probably causing the slow down and not that they aren’t working as hard as possible (unlike me) but that it takes a lot of time to implement the features they want to implement.

I would like to help out, but I don’t know Python had don’t really care that much about Python. I would had liked to develop a Trac Clone in PHP, but I really don’t have the time to try that. That said, I think Trac is fine in Python even if I can’t contribute and even if I can’t install the next version.

Something about Interwiki

There seems to be a thing about Trac that installs a bunch of Wiki pages to help you install and use Trac. Not that you really really need to have all of the wiki pages. In fact, I’m hoping this feature will allow me to get rid of all the pages and specify where they should be elsewhere on the Trac Homepage wiki site. That way, if the wiki is edited the link on my site that links to the other site will reflect the changes without me having to do any copying and pasting or having to check the main site every day.

It will also allow me to link to the Dreamhost Wiki site for such things as, I don’t know: The Trac and Subversion Installation Guide. The only problem with that is that I would have already had installed Subversion and Trac for anyone to actually see the wiki in the first place.

Waiting for 0.11

I suppose the good thing about when 0.10 is out is that 0.11 will soon be in development. I really can’t wait until I get to use the Python that is installed on my server to get rid of one step instead of having to install Python to get Clearsilver to work. This would simpify things and get rid of one step to allow more people to install Trac. I also like that it will include the Web Admin built in and I hope they will also develop a web form for signing in also.

Possibly Related Posts:

Trac and Subversion Finished

santosj — Tue, 28 Feb 2006 01:32:18 +0000

Hook Script

I have created an hook script to export the contents whenever a commit is made to the repository, that way all the changes can be viewed and debugged when the commit is made. The only other problem is that regression won’t be available, except through the subversion tool kit.

I just need to copy the hook script to the other repositories. It is really simple and should work for all repositories.

#!/usr/bin/bash svn export file://$1 /path/to/public/directory

Trac Environments

I have finished the Trac Environments and installed a couple of plugins to help with the process. It was a simple once I used the DBAuth plugin for the form based sign in and didn’t have to use any messy rewrite crap. I’m looking forward to newer versions of Trac when it comes out.

Possibly Related Posts:

More work on Trac Sites

santosj — Sat, 25 Feb 2006 21:07:22 +0000

I’m going to rework how the Trac and Development sites are set up. The main problem I believe is that I need to have all of the development sites on the same user to save time from having to download the contents and then upload them to the Subversion/Trac user. It would be a solution and keep the main web sites stable while the development sites are worked on, keeping the main development only down for the time it takes to upload the new stable one. Again this would require downloading and uploading from the Trac/Subversion user to the user hosting the main site.

trac.domain.com – Trac site with index.fcgi, admin.fcgi, and .htaccess for log in hack and redirect.

svn.domain.com

Development site for which to test the site and move the contents to the repository every day or so. A perl script could be made to only move the files that were changed to the repository, if Subversion doesn’t work well with each file being moved each time. I do wonder if it is possible to set the repository up on the domain and then still be able to test it from the browser which would allow for direct editing of the repository and keep the repository updated every time.

I could build a hook script that moves the file to the svn.domain.com directory whenever a file is checked in after being edited in the repository which would be the direct opposite of the other method. It would keep both the repository and the site up to date and allow the change to be tested on the live site. I will try this method first for each of the subversion repositories and see what needs to be done to build a ‘hook’ to updating the live site whenever the repository file is edited and checked in. This method would allow for a changelog to be accurate and only update the files that were changed. If this method doesn’t give good enough results then the first method will be used.

Conclusion

Right now all of the Trac files are on the one domain, but I’m going to expire the domain when I use the svn. and trac. instead. I think that once everything is done and working, I’m going to leave it alone and let it work for me. The only problem I can see is setting up users for the other repository developers to access and edit their game files. I’ve been using the shell to work with the repository and haven’t done the research required to set up access from outside the shell for people to work on the repository. It would be a required step and one I’m not looking forward to.

Possibly Related Posts:

Subversion+Trac 0.9.4

santosj — Wed, 22 Feb 2006 03:40:59 +0000

I spent the past three weeks working on installing Subversion and Trac to help manage the development of the game engine. I didn’t really have to spend all of the time working on it, but once I couldn’t get it to work I became obsessive over trying to get it to work. When I was finally about to give up, I got it to work. It wasn’t easy and it did require the help of a few people.

http://wiki.dreamhost.com/index.php/Trac

The link should be able to help anyone who wants to install Trac. The page is meant for those who are members of Dreamhost, but really anyone who has shell access to their host and have permissions to install software can follow the directions. It should be a lot easier for those who have root access, but I would still install trac elsewhere so that upgrading would be easier.

I am going to keep Trac up to date which shouldn’t be that hard. The web page wouldn’t have to be changed at all, but it would require upgrading the trac environment so the downtime would be five minutes or so.

Trac, I think gained some popularity because of WordPress. I didn’t really like how Bugzilla looked and it was somewhat difficult to actually see the progress. Bugzilla is working on improving and having something like Trac, but how long it will take is somewhat difficult to say. I would like to switch over to Bugzilla if they ever do add something like Trac roadmap. It is much easier to install Bugzilla than Trac and I would be able to fix any problems since I actually know a little bit of Perl. I did have Bugzilla installed at one time, but never used it.

I’m going to start working on the game now that Subversion and Trac are up and will add components and bugs a little later. I should have a roadmap done for version 0.6 a little later, once I move some of roadmap from the various pages over to Trac.

Possibly Related Posts:

Installing Trac Conclusion

santosj — Sat, 11 Feb 2006 09:10:43 +0000

Installing Trac took nearly a day of research and trying to get everything to work. With all of the time and problems, once I got to the end and it didn’t work. I didn’t want to work any more after spending all of those hours to just end in failure. I may try again in another few weeks depending on if any more information comes up on installing it.

Possibly Related Posts:

Installing Trac

santosj — Wed, 08 Feb 2006 04:46:11 +0000

Not to mention that it is a total bitch to do on Dreamhost, but it is more of the packages and the dependencies fault. It would be easier if they had an install for you, but at least they allow you to install software. Anyway, I was able to get up to the part where Subversion works and installs but installing trac is more of a problem then I had thought.

Once I do get it to work, I will set up the code base and milestones. I have been meaning to set up a bug tracker and Version Tracker to keep track of the progress of the file and games.

Possibly Related Posts: