How to prepare for future bitnami Trac update?

hi,

I noticed jphlechene’s post dated Sep 25, 2008 7:53AM (http://bitnami.org/forums/forums/18/topics/664#posts-2404) asking about the plans for an updated Trac Stack. However, my question is different but in the same area.

I am currently using Trac to manage a project and I was wondering how the update process will work before our team customizes or modifies Trac / SVN / Apache in any way, which I fear could make more difficult or jeopardize our ability to update Trac via the bitnami process.

• Once a Trac update is released, how will the update process look? (just clarify a little bit… maybe some other stacks have had an update released that you think I should take a look at?)

• Will there some script involved in the process, or will it be manual or even a split between manual and automatic?

• I know the bitnami Trac install script had source code I couldn’t read (it seemed like a binary), will the update script be open to review? The only reason I ask is given that people modify their Trac installations and may want to review what happens in an update given this fact.

• Will the bitnami Trac Stack update also include updates for SVN, Apache in addition to Trac? (Again, I don’t know what to expect)

kamko

Hi kamko,

Currently, although updating Trac to the latest version has been in our ToDo list for some time, we simply haven’t had the time to work on it. As you will probably know, there is a huge difference between Trac 0.10 and 0.11 related to their dependencies, so we have been delaying it as it does not seem as simple as updating other stacks (ie WordPress, which usually only involves using a different tarball). When will it be ready, we can’t tell. Right now, we are working on other things not only related to BitNami, and when we work on BitNami we try to fix/update/implement features in a ‘get it done’ basis. Now, answering your questions

• We usually create new installers, but not update installers (also in our ToDo list :S). What this means is that you can install the new stack somewhere else, and then migrate the contents of the old one. The application official documentation almost always explains how to do this in a detailed way.

• See previous answer, it depends on the application

• I don’t think I really understand this one

• Definitely, we try to update the dependencies before releasing a new stack

Cheers

Hey Antonio,

Trying to be thorough here with this post. Bear with me. ;)

Let me clarify on the question that you requested more information on, where you mentioned:

• I don’t think I really understand this one

So, to install trac, we install trac by using the following file (at present time this is true, at least): bitnami-trac-0.10.4-9-linux-installer.bin

Obviously, that file is a binary and we all know that is not possible for one to ‘review’ binaries in a text editor like they would source code. However, will the update from trac-0.10.4-9 to trac.-0.11 be:

a. a closed, unable to be viewed, binary file (as well) or
b. something transparent, like a script

I think some of this question could possibly have been answered when you mentioned above that you guys
“usually create new installers” for an upgrade instead of a “upgrade script”. However, I feel similarly that Trac upgrading ‘doesn’t seem as simple’ and has quite a few dependencies.

• If there’s a “new installer” then I understand that chances are it’s going to be a binary. Afterwards, system admins will just have to migrate the data.
• If it’s an ‘upgrade’ script, however, then it is possible system admins may need/want to review it?

The only reason I ask is that people modify their Trac installations, and they may want to review what happens in an update.

For instance, I use some plugins with my trac installation, so I might really need to know what’s in the update script to make sure the upgrade is compatible and so I can do testing before I certify the update for my installation of Trac. If there is a problem, I’ll like to know what I have to do to adjust my settings so that the upgrade will function. :)

Hi,

Currently we do not support upgrade installers using BitNami, so the Trac 0.11 installer will be as you guessed, a normal one. What people usually do is install the new version in a different folder (relocation and independence are two of the installers features) and then use the official migration scripts to handle the upgrade. It would be so difficult for us to support every possible update for every application we make an installer for, not to talk about third party plugins and addons.

I hope that answered your questions, do not hesitate to keep asking if you have further doubts.

Cheers