Daniel Carrera wrote:
For example, the user guide contains several guides, each of which contains several chapters, each of which may be up for review, a draft or published. IZ could not easily show these dependencies.
IZ doesn't show these dependencies, because most of the drafts are attached to the issues. Some of those make it to the site, and some do not. All are accessible to all, both source code and discussion, right there with the files!
Then, the files that get published make it to CVS. Have you checked out the CVS tree? It's pretty cool. Most projects have them. Usually, you can access them by clicking on the Version Control link in the left menu. For instance, the documentation project files are here:
http://documentation.openoffice.org/source/browse/documentation/www/
If you click on a file, you can access all sorts of information about that file, see all the versions, see the changes, download the latest. Most information in published files for each project is available in a similar tree. Each project has its own branch.
So, OOo does have the ability to handle sub-directories. :) You are right that it is not in IZ, but it is there and accessible. I was pretty excited about this discovery of the directory tree view! :) It was right under my nose, too. It's a great resource.
[...]But in any event, yes, this is a good reminder that IZ has its pros too. IZ is not a bad tool. It just makes its own set of tradeoffs.
IMHO, I think what we use (Plone I guess) is vastly superior. The ability to have sub-folders and stuff (as Daniel says) is much better.
Yup, sub-folders is good. :)
However, as much crap as issuezilla gets from users, I think it is excellent for handling bugs.
I like it both for bugs and for task handling. I think we are really lucky to have access to this resource. It is a gift, and a generous one at that.
Thank you for all you do!
:)
Diane
