diff options
| author | David Cournapeau <cournape@gmail.com> | 2009-02-27 09:13:43 +0000 |
|---|---|---|
| committer | David Cournapeau <cournape@gmail.com> | 2009-02-27 09:13:43 +0000 |
| commit | 325f05387d99a0804ea69f07fc9879930275dad0 (patch) | |
| tree | 56bf557f19549a16412ad584a521217ee4c9c520 | |
| parent | 883241ff2463f45bf7654433d6deb7833442f4f6 (diff) | |
| download | numpy-325f05387d99a0804ea69f07fc9879930275dad0.tar.gz | |
Try to hide that I can't compute how many weeks there are in a month...
| -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 641800a40..555be6863 100644 --- a/doc/release/time_based_proposal.rst +++ b/doc/release/time_based_proposal.rst @@ -28,7 +28,7 @@ Proposal Time schedule ------------- -The proposed schedule is to release numpy every 3 months - the exact period can +The proposed schedule is to release numpy every 9 weeks - the exact period can be tweaked if it ends up not working as expected. There will be several stages for the cycle: @@ -108,7 +108,7 @@ Terminology: The different frozen states are intended to be gradients. The exact meaning is decided by the release manager: he has the last word on what's go in, what -doesn't. The proposed schedule means that there would be at most 4 months +doesn't. The proposed schedule means that there would be at most 12 weeks between putting code into the source code repository and being released. Release team |