187 5353948 701 against aid allowing asin border bug building cgi chance changes companies d7 distributed documents effective email exec experience freshmeat https include integrated java list location mentioned mind normally planning pyre quick recommendation revision search security solutions table talk task tbody test third tool twisted voidspace while writes written
|
These include such things as revision or version control, branch and tip commit and merging tools, bug and issue tracking, design and documentation control, make and code compiling and building systems.
- 2009-Dec-16: Slashdot discusses task and project tracking tools. [8849]
- 2009-Feb-27: A Slashdot discussion about help desk software for small companies. [7653]
- 2009-Feb-21: A recommendation for HelpSpot, a commercial help desk application. [7616]
- 2008-Dec-25: A comparison of two bug tracking systems: Ditz and Bugs Everywhere. [7387]
- 2008-Oct-15: In First Impressions of Darcs a user new to Darcs finds that everything is a patch and the more common concept of revisions is missing. [7028]
- 2008-Jul-31: Some thoughts on what a test case/regression tracking tool should include. [6613]
- 2008-Jun-20: Experiences in writing a build system. [6393]
- 2008-Jun-11: In Deleting Roles the problems associated with deleting security roles in a bug tracking system are discussed. [6313]
- 2008-May-27: The pysvn package provides a Python interface to the subversion revision control system. This article discusses using pysvn to interact with the GoogleCode system. [6239] [1]
- 2008-Apr-17: ikaaro is a Content Management system built in Python. [5836]
- 2008-Apr-12: A feature list for project management systems. [5782]
- 2008-Apr-11: The Dr. Project team writes a bit about some of the other project management systems on the market. [5770]
- 2008-Apr-07: Using Bazaar to hack on Twisted, talks about using a DVCS (distributed version control system) to coordinate work in an off-line environment for a project that is normally tracked by a conventional centralized version control system. The discussion here is for using Bazaar to work on a project in Subversion, but the same approach could be used with other DVCS systems like Mercurial. [5617]
- 2008-Feb-10: roundup is an issue-tracking system with command line, web and email interfaces written in Python. [5075]
-
Subversion, an
aternate
version
control system, is nearing its first production release.
[5603]
- Slashdot debates source code version
control systems
[5602]
-
The WikiPedia article Comparison
of revision control software. [4747]
-
Distributed
versus pipelined builds and testing.
[4746]
-
kforge, an
open-source (GPL) system for managing software and knowledge projects.
[4745]
-
An article that has a quick overview
of many of the modern revision control systems.
[4744]
- GIT (main
page here) is the revision control
system initially developed by Linus for the Linux kernel (manual page here), he
mentions it briefly in this article. A
talk by Linus on GIT is here,
in which he rants against CVS and SVN (some of which is quite well
deserved) and even Google. Currently it it requires Cygwin to run under
Windows, and as
such, it runs slower under Windows than on a Linux host. GIT gets
mentioned
here along with a discussion of branch merging in Subversion. A brief
comparison of mercurial and git. Another comparison that
talks about how git's branching is more powerful than mercurial's. GitPython is a Python library that can work with Git repositories, so if you need to do something tedious or complicated there is a chance you could automate it with this and some Python code.
[4743]
-
A Slashdot
discussion of ticket tracking and customer management systems.
[4742]
-
A
discussion of tracking changes in the contents of files (which is
what programmers normally think of) versus changes in the name or
location of files (which is more of interest to systems administrators).
[4741]
-
A
little rant on version control, this article mentions CVS,
Subversion and some of the distributed version control systems such as
Arch, Bazaar, Mercurial and darcs.
[4740]
-
NASA
has released some of its robotics software to the public.
[4739]
-
Bug
Trackers: Do They Really All Suck? This has some good commentary on
the merits of various bug tracking (i.e. issue tracking) systems.
[4738]
-
A discussion
and performance comparison of Bazaar and Mercurial.
[4737]
-
BuildBot is an automated
build/test system.
[4736]
-
Mecurial is
a source code management system.
[4735]
-
Silva, is a content
management system (CMS) allowing for the storage, versioning, editing,
review and publication of documents by a team of authors and editors.
The document source is in XML and this allows source fragments to be
reused for various purposes.
[4734]
-
A Slashdot review of: Lean
Software Development, by Mary
and Tom Poppendieck, ISBN: 0321150783.
[4733]
-
Some projects, like the Denver
Airport's automated baggage system, end up abandoned
[4732]
-
A Slashdot article on source
code/requirements management systems
[4731]
-
Alma,
software for modeling, analyzing and converting code between languages
[4730]
-
GCJ is a GNU compiler
for Java
[4729]
-
Revision control, requirements and bug
tracking in the Linux 2.6 kernel development
[4728]
-
distcc is a tool for
distributing C/C++ compile loads across a network
[4727]
-
jxProject a project
planning tool in Java
[4726]
-
Slashdot discusses
automated software testing
[4725]
-
A Slashdot
Poll asked what revision control system Linux should switch to from
BitKeeper, while the resounding top choice was the mind meld (obviously
a very effective technique) the followup discussion has quite a bit of
feedback about the various real systems that are available. Commercial
choices include Perforce, ClearCase and BitKeeper. Free solutions
include CVS, Subversion, Arch, Monotone,
git and Bazaar-ng.
[4724]
-
trac
is an integrated wiki, bug tracker and source code management tool
written in Python
[4723]
- Codeville,
see codeville.org, this is a
distributed version control system
[4722]
|