From: Intland Software <intland.software@gmail.com>
To: git@vger.kernel.org
Subject: codeBeamer, Collaborative ALM Solution for Git and Android
Date: Mon, 14 Sep 2009 14:49:11 +0200 [thread overview]
Message-ID: <ffc57eec0909140549g619579dap8a1967f3825c121d@mail.gmail.com> (raw)
Intland Software announces the availability of codeBeamer 5.4, the
award winning Collaborative Application Lifecycle Management Solution
for distributed software development. Today's challenge is to tackle
*Android sized projects* with 2GB of code and hundreds of thousands of
change sets, and codeBeamer 5.4 is capable of processing these
repositories.
Version highlights:
* Issue escalation with hierarchic working calendars
* Calculated tracker fields with rich formula
* Wiki page editing directly in Microsoft Word
* Scalable version control management
* Major enhancements in supporting Git and Mercurial
* Revised search: more relevancy, richer query syntax, friendlier interface
Links
* Product homepage: http://www.intland.com/products/cb/overview.html
* FREE download (no expiration!):
http://www.intland.com/products/download.html#download
* FREE hosted version: http://www.intland.com/products/download.html#trial
reply other threads:[~2009-09-14 12:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ffc57eec0909140549g619579dap8a1967f3825c121d@mail.gmail.com \
--to=intland.software@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).