Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

XPTracker 699 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News XPTracker 699 (Default branch)
# 1  
Old 01-31-2008
XPTracker 699 (Default branch)
ImageXPTracker is a radical alternative agile planningtool aimed at keeping out of your way and makingsure you can see the stuff you care about at a glance.License: GNU General Public License v2Changes:
A rudimentary wiki (with no extravagant markupyet) was added. The story/task/blog entry markupwas changed from FitNesse to Markdown. The storytitle was improved. The Stripes Web framework wasupgraded. The look and feel of JavaScript windowswas unified. Help links were added to all thedescription boxes so folks can have a Markdownreference.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT HPUX

archpath

ARCHPATH(1)						      General Commands Manual						       ARCHPATH(1)

NAME

       archpath - output arch (tla/Bazaar) archive names, with support for branches

SYNOPSIS

       archpath
       archpath branch
       archpath branch--version

DESCRIPTION

       archpath is intended to be run in an arch (tla or Bazaar) working copy.

       In its simplest usage, archpath with no parameters outputs the package name (archive/category--branch--version) associated with the working
       copy.

       If a parameter is given, it may either be a branch--version, in which case archpath will output a corresponding package name in the current
       archive and category, or a plain branch name (without '--"), in which case archpath will output a corresponding package name in the current
       archive and category and with the same version as the current working copy.

       This is useful for branching.  For example, if you're using Bazaar and you want to create a branch for a new feature, you might use a  com-
       mand like this:

	      baz branch $(archpath) $(archpath new-feature)

       Or if you want to tag your current code onto a 'releases' branch as version 1.0, you might use a command like this:

	      baz branch $(archpath) $(archpath releases--1.0)

       That's much easier than using 'baz tree-version' to look up the package name and manually modifying the result.

AUTHOR

       archpath  was  written  by  Colin  Watson  <cjwatson@debian.org>.  Like archpath, this manual page is released under the GNU General Public
       License, version 2 or later.

DEBIAN
								 Debian Utilities						       ARCHPATH(1)