comparison README.devel @ 10495:f7d8b2bd7b57

README.ftp and README.devel updates
author John W. Eaton <jwe@octave.org>
date Wed, 07 Apr 2010 15:17:20 -0400
parents 66fdc831c580
children bce5b7c1a20a
comparison
equal deleted inserted replaced
10494:e52f41fd82c7 10495:f7d8b2bd7b57
1 This directory contains development snapshots of Octave. 1 This directory contains development releases of Octave.
2 2
3 If you want a stable, well-tested version of Octave, you should be 3 If you want a stable, well-tested version of Octave, you should be
4 looking at ftp://ftp.che.wisc.edu/pub/octave. 4 looking at ftp://ftp.gnu.org/gnu/octave.
5 5
6 Development snapshots are provided for people who want to help test, 6 Development releases are provided for people who want to help test,
7 debug, and improve Octave. Very little testing is done before making 7 debug, and improve Octave. Very little testing is done before making
8 the development snapshots and they may even be made when Octave is in 8 the development releases and they may even be made when Octave is in
9 an inconsistent state. It is possible that you will encounter a very 9 an inconsistent state. It is possible that you will encounter a
10 obvious bug, such as failure to compile on *any* machine. It is 10 very obvious bug, such as failure to compile on *any* machine. It is
11 likely that such bugs will be fixed by the next development snapshot, 11 likely that such bugs will be fixed by the next development release,
12 so it really isn't necessary to report them unless they persist over 12 so it really isn't necessary to report them unless they persist over
13 more than one snapshot. 13 more than one release.
14 14
15 Please DO report other bugs in the development snapshots as soon as you 15 Please DO report other bugs in the development releases as soon as you
16 find them by sending a message to maintainers@octave.org. 16 find them by sending a message to octave-maintainers@octave.org (but
17 first read the bug reporting guidelines provided at
18 http://www.gnu.org/software/octave/bugs.html).
17 19
18 If you have a fix for a bug, or an enhancement to submit, send your 20 If you have a fix for a bug, or an enhancement to submit, send your
19 patch to maintainers@octave.org. Here are some simple 21 patch to octave-maintainers@octave.org. Here are some simple
20 guidelines for submitting patches: 22 guidelines for submitting patches:
21 23
22 o Use "context diffs" for patches. A typical command for 24 o Use "context diffs" for patches. A typical command for generating
23 generating context diffs is "diff -rc octave-old octave-new". 25 context diffs is "diff -rc octave-old octave-new". If you are
26 using the Mercurial sources a patch generated with "hg export" is
27 preferred.
24 28
25 o Use the "minimalist approach" for patches. That is, each patch 29 o Use the "minimalist approach" for patches. That is, each patch
26 should address only one particular bug, new feature, etc. Do not 30 should address only one particular bug, new feature, etc. Do not
27 save up many unrelated changes and submit them all in one big 31 save up many unrelated changes and submit them all in one big
28 patch, since in general, the larger the patch the more difficult 32 patch, since in general, the larger the patch the more difficult
31 35
32 o Submit a sample ChangeLog entry with your patch. See the 36 o Submit a sample ChangeLog entry with your patch. See the
33 existing Octave ChangeLog for examples of what a ChangeLog entry 37 existing Octave ChangeLog for examples of what a ChangeLog entry
34 should look like. 38 should look like.
35 39
40 If you would like to be on the very sharpest part of the bleeding
41 edge, you can now use Mercurial to access Octave's current development
42 sources. Instructions for checking out a copy are available on the
43 web at http://www.gnu.org/software/octave/download.html.
36 44
37 Thanks, 45 Last updated: Wed, 07 Apr 2010 15:14:50 EDT
38
39 John W. Eaton
40 jwe@octave.org
41
42 Last updated: Wed, 31 Oct 2007 16:33:55 EDT