Feb 15
Devalot Version 0.1 Released
Thanks to a lot of suggestions and some patches, I think it's time to make a stable release of Devalot. I've created a release branch for version 0.1.0. People who want to play with Devalot will now have a stable place to turn, while unstable development continues.
I've updated the quick start guide to include instructions on how to obtain this release. The Subversion command to checkout the source code is what you'd expect:
$ svn co http://pmade.com/svn/oss/devalot/branches/rel/0.1 devalot-rel-0.1
And Now, Let's Break Stuff ...
The first order of business, now that we have a stable release, is to break the trunk! Okay, maybe not break it, but it is time to add our next major feature, integration with revision control systems.
Subversion will be the first revision control system to see integration with Devalot. Rest assured though, this will be done using a plugin-based system so that other revision control systems can be integrated by third-party developers.
So, What Should It Look Like?
Just like the rest of Devalot, we don't want to simply clone the existing features from another product. We want to rethink the idea of a web-based UI for revision control systems, and design something that breaks the mold and provides outstanding usability.
Where do we start, and what should it look like? Personally, I tend to turn to a web UI when I need to see a change-log of commits, and who made them, especially when I need to track commits on a branch. I'm thinking that this is where we should start.
Here is an incomplete list of features I'd like to see:
- Change-set viewer
- File browser with diff support
- Commit messages can automatically be turned into comments on an open ticket
- Automatic link generation when revisions are mentioned in pages, tickets, comments, etc.
I'd love to hear your thoughts on this feature list, and on how this data will be presented in the UI. What do you like from existing Subversion web interfaces? What don't you like? What would be the most useful way to present this information, for not only developers, but end-users as well?
Take a second, post a comment, and help shape the future of Devalot.
Duncan Beevers
Nicholas Partridge
How do you plan on linking a project to a repository? Will it be a 1-to-1 relationship? 1-to-many? Or perhaps there’s no direct link…
I love this tool. I’m doing some planning on how to best set us up using it internally, and knowing this could save me some pain later.
Peter Jones
The repository thing is a bit fuzzy. Each project will be able to establish one connection inside a given repository. That connection will include the base path to the repository, and an optional path inside the repository.
So a project can use an entire repository, or just a subset of that repository. This will allow you to create a project for the truck of your project, and one for a release branch, if you wanted to. It would also allow you to use the same repository from two different projects.
So, although it’s not modeled this way in the database or code, one repository has many projects.