[IPython-dev] Bzr install under vista + bzr olive-gtk

[Fernando Perez]

Hi Laurent,

On Mon, Mar 24, 2008 at 4:14 PM, Laurent Dufréchou
<laurent.dufrechou at gmail.com> wrote:
> Hi all,
>  Where can I put some info on how to install bzr under Vista?
>  I've installed it with the .exe that is a big error and nobody must do that.
>  So I would like to warn newcomers how to set up bzr + bzr gui tools without
>  too much pain...

That would be fantastic.   Ideally, I'd like to have more of these
docs in proper reST under source control, so I'd prefer it if you
contribute it in the docs themselves.  The right file for this would
probably be

http://ipython.scipy.org/doc/ipython1/html/development.html#version-control

which is actually in this file (lovely bzr links, if anyone knows how
to do better, let me know):

http://bazaar.launchpad.net/~ipython/ipython/ipython1-dev/annotate/ondrej%40certik.cz-20080324124519-t9fsj9phqqzue1x1?file_id=development.txt-20080302203151-17poomviavsf2zjj-18

Eventually we should have a way to have users easily edit via the wiki
these files, so that any user can contribute easily to the rest
sources without even having to send a patch, just edit a wiki page and
we get a patch automatically.  Emanuelle (Gael's super-hacker
girlfriend, who also participatedin the sprint!) has written some
tools to start building some such functionality, and Stefan may push
that further for numpy later, so I'm sure eventually we'll get all of
that.

In the meantime, just edit the source documents providing this
information in the proper place.  If you have any doubts and would
like a review, feel free to work on it on a private branch on your
+junk/ launchpad scratch area, so that others can look at it and help
you out.  Make a branch where these are the *only* changes so it's
easy for someone else to pull them, review then and give you quick
feedback without any danger of pulling changes to anything else.  Also
keep each commit reasonably small, so it's easy later to cherrypick if
needed.

We currently are nowhere near the necessary manpower to have a formal
policy of patch review before commits (such as Sage uses, for
example), but I think it's a good idea to get a bit of review when
you're becoming familiar with new parts of the tree you hadn't gone
into before.  We're also trying to be much more strict with
documentation thoroughness and testing in ipython1 than we ever were
in ip0.

Cheers,

f