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:
Clarify what a Struts Classic release will look like.

------------------------------------------------------------------------------
  
  == Special Issues ==
  
- Struts Classic 1.3.0 is a "bootstrap" distribution of the new Struts 
subprojects extracted from Struts 1.2.7: 
+ Struts Classic 1.3.0 is a "bootstrap" distribution of the new Struts 
subprojects extracted 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 term "Struts Classic" is a label for a set of 
subprojects. Struts Classic is a composite of other products.
  
+ '''struts-classic-1.3.0-bin.zip'''
-  * Apps 1.3.0
-  * Core 1.3.0
-  * EL 1.3.0
-  * Extras 1.3.0
-  * Taglibs 1.3.0
-  * Tiles 1.3.0
  
+  * struts-apps-1.3.0-bin.zip
+  * struts-core-1.3.0-bin.zip
+  * struts-el-1.3.0-bin.zip
+  * struts-extras-1.3.0-bin.zip
+  * struts-site-1.3.0-bin.zip
+  * struts-taglibs-1.3.0-bin.zip
+  * struts-tiles-1.3.0-bin.zip
+ 
- When a Struts Classic test-build passes the alpha vote,  the initial versions 
of each of these subprojects would be set at 1.3.0 (alpha). 
+ When a Struts Classic test-build passes the alpha vote, the initial versions 
of each of these subprojects would be set at 1.3.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 Struts Classic 1.3.1 distribution 
(Classic131), which, for example, might be a zip archive with the releases for: 
+ At some point, we would generate a Struts Classic 1.3.1 distribution 
(Classic131). The distribution can simply be a zip archive with the signed 
releases for each "Classic" product. For example:
  
+ '''struts-classic-1.3.1-bin.zip'''
-  * Apps 1.3.0
-  * Core 1.3.1
-  * EL 1.3.0
-  * Extras 1.3.0
-  * Taglibs 1.3.1
-  * Tiles 1.3.0
  
+  * struts-apps-1.3.1-bin.zip
+  * struts-core-1.3.0-bin.zip
+  * struts-el-1.3.0-bin.zip
+  * struts-extras-1.3.0-bin.zip
+  * struts-site-1.3.1-bin.zip
+  * struts-taglibs-1.3.1-bin.zip
+  * struts-tiles-1.3.0-bin.zip
+ 
+ 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.
+ 
- And so on. When all of the subprojects are marked GA, then the Struts Classic 
distribution can also be marked GA. On average, Apache products tend to go 
through a cycle of four to six releases before reaching GA status. 
+ When all of the subprojects are marked GA, then the Struts Classic 
distribution can also be marked GA. On average, Apache products tend to go 
through a cycle of four to six releases before reaching GA status. 
  
  == How to Help ==
  

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

Reply via email to