

! The `arch' Developer's Wiki

		   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
						+++
						bg: #d5ffff


		   *the `arch' revision control system*

 		   *project home page*: http://www.regexps.com/arch.html

		   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



This is a wiki for notes used to keep track of the status
of [`arch'] development.

`arch' is an amazingly cool revision control system, publicly
distributed under the terms of the GNU General Public License.  `arch'
features distributed repositories, whole-tree patch sets, extensive
logging, support for renames, the ability to access archived revisions
using ordinary programming tools (e.g. `diff -r' or `find' and
`grep'), excellent support for developing on branches, and easy
integration into automated software engineering processes.  Early
adopters of `arch' have reported that they find it to have a natural
design, especially well integrated with standard unix development
environments.  `arch' is self hosting with its author and some of the
volunteer contributors each maintaining their own repositories.

I'm estimating that, with a little luck, the 1.0 release is only a few
months away.  Of course, that's assuming I find a way to work part
time with a few people who are working full time on scaling it up to
handle very large systems;  absent that, well ... my personal "itches"
for this code are very nearly all "scratched" ...


v================================
				+++
				width: 100
				bg: #d5d5ff
				headers: no
				

			 + __project info__+

+ [`arch']			:::	the project home page

+ [downloading]			:::	the FTP area

+ ReleaseNews			:::	what's new?

+ [manual]			:::	an on-line copy of the

			 + __developer notes__+

+ UsabilityRelease	:::	Notes about what's planned for the upcoming
				"usability enhancements" release.

+ BigIssues		:::	Notes on the big issues for a 1.0 release.

+ LarchAliases		:::	A rough spec of a new feature for
				command aliases.

+ OptionStandards	:::	A rough spec of the standard for
				command line options for `arch' commands.

+ ArchPrinciples	:::	Buzzwords to meditate upon.

			    + __links__+

+ SFTP support		:::	Until it's merged in to the main release,
				You can find Scott Parish's
				patches-in-progress for SFTP and
				"""WebDAV support in his archive (archive
				name `software@srparish.net', location
				`ftp://ftp.srparish.net/pub/{archive}').

+ Variaions in Perl	:::	You can find Jonathan Geisler's
				rapidly progressing perl version of
				arch in his archive,
				`geisler@ece.nwu.edu', located at
				`ftp://ece.nwu.edu/pub/geisler/public_archive'. 



		    +__self hosting repository__+

If you have `arch' up and running, you can get the latest sources from
my repository:

<<<
    % larch register-archive lord@regexps.com--2002 \
			     ftp://regexps.com/pub/{archive-2002}
    % larch get lord@regexps.com--2002/dists--devo--1.0 arch
    % cd arch
    % larch build-config regexps.com/devo.arch
>>>

^================================


v================================
				+++
				width: 100
				bg: #d5d5ff
				headers: no
				

	   + __approximate list of things "coming soon"__ +

+ BugReports		:::	The database of known bugs and their
				statuses.


+ UnscheduledTodoItems	:::	A big bag of TODO items not yet
				scheduled for any particular release.

+ PerlArch		:::	A set of similar pages, dedicated to
				the implementation of `arch' in Perl.
	
+ TestSuite		:::	A set of pages dedicated to the `arch'
				test suite.

+ FormalSpecs		:::	A set of pages dedicated to the formal
				specification of `arch'.

+ ReleaseHistory	::: 	A record of releases made and the experiences
				they led to.  Eventually, test suite
				results for releases.

+ BranchTesting		:::	Test suite results for selected development
				branches.

+ ArchDesignMemos	:::	An index and status for the [Arch-tech
				Design Memos] process at it pertains
				to the `arch' revision control system.

+ NewPatchSetFormat	:::	Design documents for the new
				`mkpatch' and `dopatch' programs
				in the `file-utils' package.

+ PerformanceNotes	:::	Design documents about the performance
				goals for `arch'.

+ SmartServers		:::	Ok, let's suppose we decide to support
				`HTTP' transport in `with-ftp'.  If we
				want more than read-only access, that
				requires some `arch'-specific smarts
				on the server side.  So this is an opportunity
				to add all kinds of interesting things
				like server-side triggers and
				fine-granularity access protection.
				The CGI library in the implmentation
				of LabNotes/ gives us all sorts of
				useful building blocks from which to
				build customized `arch' servers.

^================================

*references*

[`arch']:: http://www.regexps.com/arch.html

[Arch-tech Design Memos]:: http://www.regexps.com/adm-process.html

[downloading]:: ftp://ftp.regexps.com/pub/src/arch

[manual]:: http://www.regexps.com/src/docs.d/arch/html/arch.html

---
%%% tag: Tom Lord Wed May  1 23:20:14 2002 (ArchRevCtl.d/IntroTopic)
%%%
