[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bzr repository ready?

From: Eli Zaretskii
Subject: Re: bzr repository ready?
Date: Fri, 20 Nov 2009 15:34:36 +0200

> From: Karl Fogel <address@hidden>
> Date: Thu, 19 Nov 2009 00:31:20 -0500
> Cc: Andreas Schwab <address@hidden>,
>       Jason Earl <address@hidden>,
>       Ian Clatworthy <address@hidden>, address@hidden
> Alan Mackenzie <address@hidden> writes:
> > Please wait until the 23.2 pretest is out.  It's only a few more days
> > (?end of November?).
> Sure -- makes sense to me.

Also, would it be possible to publish a short ``howto'' cookbook for
those who are not familiar enough with bzr?  A DVCS has more different
workflows than CVS and its ilk, so it would be good if active
developers could know up front how to set up and how to use the
workflow that best fits their needs, without having to read lots of
unnecessary documentation and finding that out by trial and error.  At
least the following important workflows come to mind:

 . Development on the trunk -- sync with the main repository, make
   changes, submit them back to the repository.

 . Development on a release branch -- same as above, except that
   changes go to a branch.

 . Development on a public branch -- this would include more merges
   from and to the trunk, and otherwise is like the second bullet

 . Development on a private branch.

(Maybe there are more -- I have no real experience with a DVCS, so I
don't know.)

For each one of these, it would be enough to point to the relevant
sections of the existing bzr docs, no need to rewrite them, unless
some of the issues are mal-documented.

In addition, some guidelines for selecting the right version of bzr
that should be installed, and if there are more than one that's
suitable, a short list of advantages and disadvantages of each of

Finally, some guidance for users on Windows, if there are any issues
that need special attention (EOL format comes to mind, as well as
binary files, but maybe there's more).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]