From a4cb02488277e175c2e12c25f96213b20fd429af Mon Sep 17 00:00:00 2001 From: dsyer Date: Mon, 3 Mar 2008 18:19:12 +0000 Subject: [PATCH] Update version numbers --- src/site/apt/downloads.apt | 8 ++++---- src/site/apt/getting-started.apt | 2 -- src/site/apt/snapshots.apt | 2 +- src/site/fml/faq.fml | 22 +++++++++++----------- 4 files changed, 16 insertions(+), 18 deletions(-) diff --git a/src/site/apt/downloads.apt b/src/site/apt/downloads.apt index fedd6e4b1..8962bad99 100644 --- a/src/site/apt/downloads.apt +++ b/src/site/apt/downloads.apt @@ -7,11 +7,11 @@ Milestone Builds - These builds are provided for evaluation and community feedback. They will have a release identifier ending in "mX" where X is the milestone number. The current release is <<1.0.0.m4>>. + These builds are provided for evaluation and community feedback. They will have a release identifier ending in "mX" where X is the milestone number. The current release is <<1.0.0.m5>>. * Zip Downloads - Starting with Spring Batch 1.0.0.m4 there are ZIP based artifacts that contain the release JARs. You can find those releases {{{http://static.springframework.org/downloads/nightly/milestone-download.php?project=BATCH}here}}. There are two ZIP files in the release. The first zip file is called <<>>. This file contains only the JAR files for the release. The second zip file is called <<>>. This file contains the JAR files for the release as well as all of the third-party dependencies for the release. In addition, this release contains the Spring Batch source code including the samples and their third-party dependencies as well. + There are ZIP based artifacts that contain the release JARs. You can find those releases {{{http://static.springframework.org/downloads/nightly/milestone-download.php?project=BATCH}here}}. There are two ZIP files in the release. The first zip file is called <<>>. This file contains only the JAR files for the release. The second zip file is called <<>>. This file contains the JAR files for the release as well as all of the third-party dependencies for the release. In addition, this release contains the Spring Batch source code including the samples and their third-party dependencies as well. * Maven Artifacts @@ -33,7 +33,7 @@ Milestone Builds org.springframework.batch spring-batch-core - 1.0.0.m4 + 1.0.0.m5 +--------------- @@ -43,7 +43,7 @@ Milestone Builds org.springframework.batch spring-batch-execution - 1.0.0.m4 + 1.0.0.m5 +--------------- diff --git a/src/site/apt/getting-started.apt b/src/site/apt/getting-started.apt index 162be0f98..865fb0046 100644 --- a/src/site/apt/getting-started.apt +++ b/src/site/apt/getting-started.apt @@ -9,8 +9,6 @@ Spring Batch Getting Started A convenient way to get started quickly with Spring Batch is to run the samples which are packaged in the samples module. The source code for the samples (and the other modules) is available either from the {{{downloads.html}.Zip assembly}} or from {{{source-repository.html}Subversion}}. - These instructions work with the "m4" .Zip distribution. - * Using the .Zip Distribution ** With Eclipse and without Maven diff --git a/src/site/apt/snapshots.apt b/src/site/apt/snapshots.apt index 6c96b58ba..1da9889ef 100644 --- a/src/site/apt/snapshots.apt +++ b/src/site/apt/snapshots.apt @@ -27,7 +27,7 @@ Snapshot Builds org.springframework.batch spring-batch-core - 1.0.0.m4-SNAPSHOT + 1.0.0.rc1-SNAPSHOT +--------------- diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml index a9c6df090..8799d352e 100644 --- a/src/site/fml/faq.fml +++ b/src/site/fml/faq.fml @@ -8,7 +8,7 @@ correct? - We expect m3, m4, rc1 before 1.0 final, so realistically + We expect rc1 before 1.0 final, so realistically not soon. You can track the progress and planning in JIRA (http://opensource.atlassian.com/projects/spring/browse/BATCH). @@ -27,8 +27,8 @@

- We are still in the milestone release phase (1.0-m4 - is in the pipeline). This means that we are still + We are still in the milestone release phase (1.0-m5 + is just out). This means that we are still adding functionality that we want to be part of a 1.0 release. We do not rule out changes to package and interface names in this phase, but that said we @@ -62,14 +62,14 @@ Multi-threaded execution in a single VM is perfectly - possible with 1.0 - but we recommend exercising caution - in the analysis of such requirements (is it really - necessary?). Several people have tried it and there are - some issues with restartability (plus the usual - documentation requests), but otherwise it should work. - With a little more effort starting in m4 it should work - even better, but we aren't planning to solve the - restartability problem until after 1.0. + possible with 1.0 - but we recommend exercising + caution in the analysis of such requirements (is it + really necessary?). Several people have tried it and + it works as long as the step is intrinsically + restartable (idempotent effectively). The parellel + job sample shows how it might work in practice - this + uses a "process indicator" pattern to mark input + records as complete, inside the business transaction.