diff options
| author | David Cournapeau <cournape@gmail.com> | 2009-02-27 07:24:17 +0000 |
|---|---|---|
| committer | David Cournapeau <cournape@gmail.com> | 2009-02-27 07:24:17 +0000 |
| commit | 85adad9c4fca1302e0617841753a840b7093bfd9 (patch) | |
| tree | 7a75127c14f2c295dedeccbfe79065dd7a47948d | |
| parent | eb8892e8d75dcdca50c821f92cce6d33905afd94 (diff) | |
| download | numpy-85adad9c4fca1302e0617841753a840b7093bfd9.tar.gz | |
Spelling in time-based release doc.
| -rw-r--r-- | doc/release/time_based_proposal.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/release/time_based_proposal.rst b/doc/release/time_based_proposal.rst index 1e45eae65..ae94ad4b2 100644 --- a/doc/release/time_based_proposal.rst +++ b/doc/release/time_based_proposal.rst @@ -4,11 +4,11 @@ Introduction ============ This document proposes some enhancements for numpy and scipy releases. -Successive numpy and scipy releases are too far appart from a time point of +Successive numpy and scipy releases are too far apart from a time point of view - some people who are in the numpy release team feel that it cannot improve without a bit more formal release process. The main proposal is to follow a time-based release, with expected dates for code freeze, beta and rc. -The goal is two folds: make release more predictible, and move the code forward. +The goal is two folds: make release more predictable, and move the code forward. Rationale ========= |