Main > Free Download Search >

Free bazaar vcs software for mac

bazaar vcs

Sponsored Links
Sponsored Links
Sort by >> Relevance
rss
Secleted [ 0 ] software to compare
Results 1 - 15 of about 6
Bazaar VCS 1.8 RC1 / 1.7.1

Bazaar VCS 1.8 RC1 / 1.7.1


Free and open source application that adapts to the workflows you want to use more>> <<less
Download (3.6MB)
Added: 2008-10-08 License: GPL Price: FREE
391 downloads
Bazaar 1.16 RC1 / 1.15.1

Bazaar 1.16 RC1 / 1.15.1


Free and open source application that adapts to the workflows you want to use Bazaar is a distributed version control system available under the GPL that reduces barriers to participation in your more>> Free and open source application that adapts to the workflows you want to use

Bazaar is a distributed version control system available under the GPL that reduces barriers to participation in your project.
Bazaar is designed to support Mac OS, GNU/Linux, UNIX, Windows. In summary, Bazaar gives you fast, distributed revision control that "Just Works", supporting renames of directories and files smoothly.
Bazaar is designed to maximise the level of community participation in your project.
Bazaar branches can be published on any web server, and uploaded over sftp, ftp, or rsync. If you want the fastest possible network performance, there is a smart server.
Bazaar supports flexible work models: centralized like cvs or svn, commit offline, enforced code review when desired, and automatic regression testing.
Decentralized revision control systems give people the ability to collaborate more efficiently over the internet using the bazaar development model and have many other advantages.
When you use Bazaar, you can commit to your own local branches of your favourite free software projects without needing special permission.

Main features:
Good performance:
- Bazaar status in a tree of 5,000 files takes just 0.5 seconds, so almost every open source project can get the advanced features of Bazaar without slowing down its developers. Bazaar is robust in the face of radical tree restructuring, saving you time when it comes to merging from your community.
Safe with your data:
- There have not been any data loss bugs in a Bazaar release in the past two years. Bazaar has a huge test suite that ensures that new file formats can be tested automatically. The development process follows best practice with code review of all core and community code landings.
Friendly:
- Bazaar "Just Works" (which is why the Ubuntu team chose it for their project). Bazaar has a natural feel, you can publish your code on any web server or use a custom server for performance. Bazaar has perfect support for renaming files AND directories, which means you can unleash your community and merge efficiently even from contributors who are radically restructuring the tree.
Free:
- Bazaar is available under the GPL v2 or later.
Easy to integrate:
- Bazaar is designed as a Python API with a plugin system, so it is easy to embed in your tools and projects and easy to extend or integrate with existing infrastructure. Whether you are managing your development, or keeping track of configuration files, or building a new content management system, Bazaar is a great choice if you like to work in Python.

System requirements:
-

Enhancements
Compatibility Breaks:
- Display prompt on stderr (instead of stdout) when querying users so that the output of commands can be safely redirected. (Vincent Ladeuil, #376582)
New Features:
- A new repository format 2a has been added. This is a beta release of the the brisbane-core (aka group-compress) project. This format now suitable for wider testing by advanced users willing to deal with some bugs. We would appreciate test reports, either positive or negative. Format 2a is substantially smaller and faster for many operations on many trees. This format or an updated version will become the default in bzr 2.0.
- This is a rich-root format, so this repository format can be used with bzr-svn. Bazaar branches in previous non-rich-root formats can be converted (including by merge, push and pull) to format 2a, but not vice versa. We recommend upgrading previous development formats to 2a.
- Upgrading to this format can take considerable time because it expands and more concisely repacks the full history.
- If you use stacked branches, you must upgrade the stacked branches before the stacked-on branches. (See )
- --development7-rich-root is a new dev format, similar to --dev6 but using a Revision serializer using bencode rather than XML. (Jelmer Vernooij, John Arbash Meinel)
- mail_client=claws now supports --body (and message body hooks). Also uses configured from address. (Barry Warsaw)
Improvements:
- --development6-rich-root can now stack. (Modulo some smart-server bugs with stacking and non default formats.) (John Arbash Meinel, #373455)
- --development6-rich-root delays generating a delta index for the first object inserted into a group. This has a beneficial impact on bzr commit since each committed texts goes to its own group. For committing a 90MB file, it drops peak memory by about 200MB, and speeds up commit from 7s => 4s. (John Arbash Meinel)
- Numerous operations are now faster for huge projects, i.e. those with a large number of files and/or a large number of revisions, particularly when the latest development format is used. These operations (and improvements on OpenOffice.org) include: branch in a shared repository (2X faster), branch --no-tree (100X faster), diff (2X faster), tags (70X faster) (Ian Clatworthy)
- Pyrex version of bencode support. This provides optimized support for both encoding and decoding, and is now found at bzrlib.bencode. bzrlib.utils.bencode is now deprecated. (Alexander Belchenko, Jelmer Vernooij, John Arbash Meinel)
Bug Fixes:
- Bazaar can now pass attachment files to the mutt email client. (Edwin Grubbs, #384158)
- Better message in bzr add output suggesting using bzr ignored to see which files can also be added. (Jason Spashett, #76616)
- bzr pull -r 123 from a stacked branch on a smart server no longer fails. Also, the Branch.revision_history() API now works in the same situation. (Andrew Bennetts, #380314)
- bzr serve on Windows no longer displays a traceback simply because a TCP client disconnected. (Andrew Bennetts)
- Clarify the rules for locking and fallback repositories. Fix bugs in how RemoteRepository was handling fallbacks along with the _real_repository. (Andrew Bennetts, John Arbash Meinel, #375496)
- Fix a small bug with fetching revisions w/ ghosts into a new stacked branch. Not often triggered, because it required ghosts to be part of the fetched revisions, not in the stacked-on ancestry. (John Arbash Meinel)
- Fix status and commit to work with content filtered trees, addressing numerous bad bugs with line-ending support. (Ian Clatworthy, #362030)
- Fix problem of "directory not empty" when contending for a lock over sftp. (Martin Pool, #340352)
- Fix rule handling so that eol is optional, not mandatory. (Ian Clatworthy, #379370)
- Pushing a new stacked branch to a 1.15 smart server was broken due to a bug in the BzrDirFormat.initialize_ex smart verb. This is fixed in 1.16, but required changes to the network protocol, so the BzrDirFormat.initialize_ex verb has been removed and replaced with a corrected BzrDirFormat.initialize_ex_1.16 verb. 1.15 clients will still work with a 1.16 server as they will fallback to slower (and bug-free) methods. (Jonathan Lange, Robert Collins, Andrew Bennetts, #385132)
- Reconcile can now deal with text revisions that originated in revisions that are ghosts. (Jelmer Vernooij, #336749)
- Support cloning of branches with ghosts in the left hand side history. (Jelmer Vernooij, #248540)
- The bzr diff now catches OSError from osutils.rmtree and logs a helpful message to the trace file, unless the temp directory really was removed (which would be very strange). Since the diff operation has succeeded from the users perspective, no output is written to stderr or stdout. (Maritza Mendez, #363837)
- Translate errors received from a smart server in response to a BzrDirFormat.initialize or BzrDirFormat.initialize_ex request. This was causing tracebacks even for mundane errors like PermissionDenied. (Andrew Bennetts, #381329)
Documentation:
- Added directory structure and started translation of docs in Russian. (Alexey Shtokalo, Alexander Iljin, Alexander Belchenko, Dmitry Vasiliev, Volodymyr Kotulskyi)
API Changes:
- Added osutils.parent_directories(). (Ian Clatworthy)
- bzrlib.progress.ProgressBar, ChildProgress, DotsProgressBar, TTYProgressBar and child_progress are now deprecated; use ui_factory.nested_progress_bar instead. (Martin Pool)
- graph.StackedParentsProvider is now a public API, replacing graph._StackedParentsProvider. The api is now considered stable and ready for external users. (Gary van der Merwe)
- bzrlib.user_encoding is deprecated in favor of get_user_encoding. (Alexander Belchenko)
- TreeTransformBase no longer assumes that limbo is provided via disk. DiskTreeTransform now provides disk functionality. (Aaron Bentley)
Internals:
- Remove weave.py script for accessing internals of old weave-format repositories. (Martin Pool)
Testing:
- The number of cores is now correctly detected on OSX. (John Szakmeister)
- The number of cores is also detected on Solaris and win32. (Vincent Ladeuil)
- The number of cores is also detected on FreeBSD. (Matthew Fuller)

<<less
Download (4.8MB)
Added: 2009-06-13 License: GPL Price: FREE
182 downloads
 
Other version of Bazaar
Bazaar 1.15.1using the bazaar development model and have many other advantages. When you use Bazaar, you can ... data loss bugs in a Bazaar release in the past two years. Bazaar has a huge test suite that ensures
Price: FREE
License:GPL
Download (4.1MB)
191 downloads
Added: 2009-06-10
Releaser 0.2.4

Releaser 0.2.4


Set of scripts to help manage and automate software package releases more>> Set of scripts to help manage and automate software package releases

Releaser is a set of scripts to help manage and automate software package releases. Every software package should have a .pkg file containing necessary information about the project and modules to be used.

The prerel script runs the selected pre/ modules and uses the .pkg information and the input from the user to generate a release specific .rel file. Typical tasks in pre modules include generation of changelogs, building of tarballs from vcs repositories, etc.

postrel uses the .rel and other output of the pre scripts to actually execute the release by running the post modules, this usually includes uploading tarballs, sending announcements to m ailing lists, uploading news page in website, freshmeat submission, etc.

<<less
Download (21KB)
Added: 2008-10-05 License: Freeware Price: FREE
384 downloads
TracGViz 1.3.4

TracGViz 1.3.4


TracGViz is a complete and useful package (plugin) which provides components so that Trac be able to use widgets and related technologies offered by Google. more>>

TracGViz 1.3.4 is a complete and useful package (plugin) which provides components so that Trac be able to use widgets and related technologies offered by Google.

Major Features:

  1. It allows to feed data managed by Trac to widgets based on Google Visualization API.
  2. It allows embedding iGoogle Gadgets in wiki pages using WikiFormatting.

Enhancements:

  • New ! GVizQuickJumpEntries offers data about interesting places in the repository (a.k.a. quick jump entries). This includes tags and branches, for instance. The data is provided by VersionControlRPC.
  • Bug fixed: Formerly all revisions were included in the revision log if only individual revisions were requested. Now the result sets include just the information for the particular changesets supplied in rev parameter. Tested with both hg and svn.
  • Bug fixed: Exception with message Invalid list index was raised when using Subversion backend when requesting the log for individual revisions. This works OK now for both hg and svn.
  • Bug fixed: Wrong default value for fmt parameter in GVizChangesetDetails. Now it's OK.
  • Bug fixed: Formerly undocumented column in GVizTimelineFilters provider now contains appropriate description.
  • WikiFormatting may be used to document the data sources. It may be included in the documentation written for parameters, columns, and the data source itself.
  • Bug fixed: Documentation for providers having dynamic schemas was not previously rendered. This has been fixed and a new property has been added in docs to highlight whether the data source returns always the same columns or if they can vary depending upon run-time conditions.
  • Milestones may be filtered by name by providing a UNIX pattern in filter_by parameter.
  • UNIX filename patterns are compiled using REs for better performance.
  • Bug fixed: When using Hg backend, the code in version 1.3.3 in order to revisions iterator (VCS RPC) entered infinite loop (under certain conditions apparently related to branching or version numbers). This doesn't happen anymore.
  • Bug fixed: Now VCS RPC retrieves all changesets when using Hg backend. The implementation doesn't guess anymore the revision order and retrieves all that information directly from the underlying VCS connector in use. The former algorithm was weak because it only considered the first parent of a given revision. Therefore many others (especially all those in different branches) were missing from the result set.
  • Individual revisions (and not just intervals like before) may be selected in GVizChangesets (i.e. to obtain the revision log).
  • Bug fixed: As a consequence of the changes introduced in version 1.3.3 (especially in ReportRPC and VersionControlRPC) together with bug #5586@TH.org in XmlRpcPlugin, made impossible to render the main displaying documentation about the different RPC handlers. Both docstrings have been modified and everything is back to normal right now.


<<less
Download (119KB)
Added: 2009-08-02 License: Freeware Price: FREE
downloads
VOODOO Server 2.1.4

VOODOO Server 2.1.4


Version control system for CodeWarrior. more>>
VOODOO Server is a version control system for software developers using Metrowerks CodeWarrior under Mac OS.
VOODOO Server and the plug-in included, CodeWarrior, provide reliable and robust version control without adding the administrative overhead that often accompanies version control.
Its cubic project mart structure builds the robust foundation for version management without limits. VOODOO Servers CodeWarrior plug-in lets you track all your files from inside the CodeWarrior IDE.
Its object-oriented branching makes it unique in the competitive arena.
Enhancements:
Problems Fixed:
- Mac OS X 10.4 (Tiger) compatibility
- This version has been prepared for Mac OS X 10.4 (Tiger). Incompatibilities (e.g., permission errors upon opening the database) have been fixed.
- CW Plug-in: disconcerting conflict alerts
- The CW plug-in is more careful about showing conflict alerts when performing check-in/check-out operations.
- CW Plug-in: compare helper popup menu doesnt show any options The compare helper popup menu in the "Browse History" and "Check In" dialog didnt show any options for files with an unspecified file type (i.e., ????). The plug-in now uses both the file type and the file extension to determine the set of possible compare helper applications for a file.
- CW Preferences Panel: Error -10814 The panel no longer treats error -10814 (kLSApplicationNotFoundErr) as a generic error, but shows a meaningful error message instead.
- Server: privilege check when adding part to project
The server application didnt correctly check for privileges when trying to add a part to a project.
- Server: users with "read access" cannot fetch files
Under certain circumstances the server did not allow a file to be fetched, if a user had only read access to a part.
- AppleScript "Setup Version Control" fails
The "Setup Version Control" script failed, because the VCS panel erroneously returned a "parameter missing" error.
<<less
Download (6.5MB)
Added: 2007-04-20 License: Freeware Price:
917 downloads
Parabuild 4.0.0 EAP Build 1670 / 3.2.35

Parabuild 4.0.0 EAP Build 1670 / 3.2.35


Software build and release management system more>>
Parabuild 4.0.0 EAP Build 1670 / 3.2.35 provides you with an outstanding and powerful software which can build and release management system. Parabuild helps software teams and organizations reduce risks of project failures by providing continuous integration and delivering practically unbreakable scheduled builds.

Note: Parabuild is free for non-commercial use.

Major Features:

  1. Software Release Management:
    • Release builds
    • Practically unbreakable nightly builds
    • Continuous integration
    • Multi-platform remote builds
    • Parallel builds
    • Manual patch builds
    • Fine-grained scheduling
    • Shell scripts, make, ANT, NAnt, MSBuild, Perl, qmake, ElectricAccelerator, MSDEV, nmake,Maven, Jam and VB
  2. Version Control Integration:
    • Support for Perforce, Subversion, CVS, Surround SCM, ClearCase, Serena ChangeMan (PVCS), Visual SourceSafe, Borland StarTeam, SourceGear Vault, and MKS Source Integrity
    • Change lists
    • Multi-line VCS repository paths
    • Build labeling/tagging
  3. Web User Interface:
    • Fast, easy to use Web user interface (UI)
    • No more digging through configuration files
    • Dashboard and detailed views of builds statuses
    • Integration with Cenqua FishEye
    • Integration with ViewCVS/ViewVC
  4. Statistics And Build Telemetry:
    • Build time
    • Build and change trends
    • Build breakage distribution
    • Test statistics
  5. Build Archive and Search:
    • Text, HTML, Clover, Cobertura, JUnit, PMD, and findbugs logs
    • Searchable build log archive
    • Online build results access
    • Automatic archive cleanup
  6. Notification:
    • E-mail
    • RSS
    • Windows system tray
    • Instant messaging (IM)
  7. Simple Administration:
    • Simple three minutes installation
    • Low to zero administration overhead
    • Management through Web UI
    • System stability monitoring
    • Group based security
    • LDAP authentication
  8. Issue Tracking Systems Integration:
    • Jira
    • Bugzilla
    • Perforce jobs
    • Integration with ViewCVS and P4Web
  9. Test Tools Integration:
    • Rendering JUnit reports
    • JUnit statistics charts
  10. Compliance And IT Governance:
    • Know who, when, what, how and why.
    • Build configuration audit
    • Change lists
Enhancements:
  1. Build Management:
    • Build load balancing and failover through clusterization of remote build agents
    • Sticky build agents
    • Clean checkout on agent change
    • Online charts with build agent statuses and load
    • Keeping paused status after re-start
    • Queuing serialized builds if all agents are busy
    • Page to monitor remote agents
    • Environment variables PARABUILD_PROJECT_ID, PARABUILD_PROJECT_NAME, PARABUILD_BUILD_ID, PARABUILD_LAST_GOOD_BUILD_NUMBER, PARABUILD_LAST_GOOD_BUILD_TIME, PARABUILD_LAST_GOOD_CHANGE_LIST_NUMBER and PARABUILD_LAST_GOOD_CHANGE_LIST_TIME
    • Stopping and resuming a group of builds
    • Converting build schedule from manual to automatic and from automatic to manual
  2. Web UI:
    • Pop-up editor for build commands
    • Builder drop-down on the build configuration screen
    • Displaying builds assigned to a particular agent machine
    • Build instructions section
    • Display group to show only scheduled builds
    • IP Address and next build time on build list
    • Allowing higher number for cool-down interval
    • Information on who stopped the build to build status screens
    • Colored markers for stdout logs
    • Notification settings in the read-only build run configuration view
    • Throbbers on detailed build status
    • Change list number in build history table
    • Simplified navigation for system administration
    • Wide layout and notes for builds history
    • Build name and host in the error messages
    • Build name and host on the error list page
    • Notifying all administrators about build errors
    • Support for configuring MKS dates
  3. Version Control Integration:
    • Perforce: Graceful handling of erroneous double slashes in Perforce depot path
    • Accurev: Added integration with AccuRev VCS
    • Subversion:
      • Accepting the SSL certificate automatically when accessing https location
      • Watching non-recursive Subversion paths recursively for changes
      • Delay between polling multiple Subversion paths
      • Cleaning up workspace on agent change
    • Notification:
      • Global VCS user to e-mail map
      • Global setting for ignoring user name case when resolving e-mails of Perforce users
      • Improved option "Send failures only once"
    • Log Management:
      • Ignoring directory time stamp for logs
      • Integration with Boost Unit Test Framework
      • Generic test result handler
    • Installation & Environment:
      • Ability to start and stop Parabuild service from Parabuild program group under Windows
      • Enabling running remote builder under Windows under Administrator user
      • Support for 8GB database files
    • Security: Allow users with edit or start rights on any build to see system errors
<<less
Download (19.6MB)
Added: 2009-05-29 License: Freeware Price: FREE
12 downloads
Secleted [ 0 ] software to compare
  • Page: 1 of 1
  • 1