Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Struts Wiki" for change 
notification.

The following page has been changed by TedHusted:
http://wiki.apache.org/struts/StrutsClassicRelease130

The comment on the change is:
Changes per discussions on dev@

------------------------------------------------------------------------------
  
  == Special Issues ==
  
- Struts Classic 1.3.0 is a "bootstrap" initiative to extract seven new Struts 
subprojects from Struts 1.2.7. When these subprojects are ready for independent 
distribution, each will be available independently and in a single, convenient 
ZIP archive. The archive will include the original "seven dwarfs" along with 
any other Struts subprojects that are compatible with Struts Core 1.3.0 (or 
later). 
+ Struts Classic 1.3.0 is a "bootstrap" initiative to extract seven new Struts 
subprojects from Struts 1.2.7. When these subprojects are ready for independent 
distribution, each will be available independently and in a single, convenient 
ZIP archive. The archive will include the JARs for the original "seven dwarfs" 
along with any other Apache Struts subprojects that are compatible with the 
latest GA release of Struts Core.
  
- '''struts-core-library-bin-test.zip'''
+ '''struts-core-library-1.3_00.zip'''
  
-  * struts-apps-1.3.0-bin.zip
+  * struts-apps-1.3.0.jar
-  * struts-core-1.3.0-bin.zip
+  * struts-core-1.3.0.jar
-  * struts-el-1.3.0-bin.zip
+  * struts-el-1.3.0.jar
-  * struts-extras-1.3.0-bin.zip
+  * struts-extras-1.3.0.jar
-  * struts-faces-1.0.0-bin.zip
-  * struts-flow-1.0.0-bin.zip
-  * struts-scripting-1.0.0-bin.zip
-  * struts-site-1.3.0-bin.zip
+  * struts-site-1.3.0.jar 
-  * struts-taglibs-1.3.0-bin.zip
+  * struts-taglibs-1.3.0.jar
-  * struts-tiles-1.3.0-bin.zip
+  * struts-tiles-1.3.0.jar
+  * ... other dependencies as needed
  
  When a Struts Core Library test-build passes the alpha vote, the initial 
versions of each of the original subprojects would be set at 1.3.0 (alpha). New 
subprojects will be set at 1.0.0 (alpha). 
  
  If fixes need to be made to any of these subprojects, or if dependendencies 
are updated, then a new release of that subproject can be rolled and released 
in the usual way, under its own release plan.
  
- At some point, we would generate a new distribution with the GA versions of 
each product. For example:
+ At some point, we would generate a new distribution with the GA versions for 
each product. For example:
  
- '''struts-core-library-bin-001.zip'''
+ '''struts-core-library-1.3_01.zip'''
  
-  * struts-apps-1.3.1-bin.zip
+  * struts-apps-1.3.1.jar
-  * struts-core-1.3.0-bin.zip
+  * struts-core-1.3.0.jar
-  * struts-el-1.3.0-bin.zip
+  * struts-el-1.3.0.jar
-  * struts-extras-1.3.0-bin.zip
+  * struts-extras-1.3.0.jar
-  * struts-faces-1.0.0-bin.zip
-  * struts-flow-1.0.0-bin.zip
+  * struts-faces-1.3.0.jar
+  * struts-flow-1.3.0.jar
-  * struts-site-1.3.1-bin.zip
+  * struts-site-1.3.1.jar
-  * struts-scripting-1.0.0-bin.zip
+  * struts-scripting-1.3.0.jar
-  * struts-taglibs-1.3.1-bin.zip
+  * struts-taglibs-1.3.1.jar
-  * struts-tiles-1.3.0-bin.zip
+  * struts-tiles-1.3.0.jar
+  * ... other dependencies as needed
  
- Note that some products may advance to their own "1.3.1" versions, but others 
may not. Each Struts product has it's own release cycle *independant* of all 
other Struts products. On average, Apache products tend to go through a cycle 
of four to six releases before reaching GA status. When a subproject has a new 
GA release, the library distribution would be updated, and the version counter 
incremented.
+ Note that some products may advance to their own "1.3.1" versions, but others 
may not. Each Struts product has its own release cycle *independant* of all 
other Struts products. On average, Apache products tend to go through a cycle 
of four to six releases before reaching GA status. When a subproject has a new 
GA release, the library distribution would be updated, and the version counter 
incremented.
  
  == How to Help ==
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to