Changes between Version 3 and Version 4 of proposals/release_strategy

Timestamp:

Apr 28, 2010, 7:52:44 AM (14 years ago)

Author:

fxp

Comment:

--

proposals/release_strategy

@@ -13 +13 @@
 
 But some points needs clarification: 
- * We don't have automatic build system.
+ * We don't have automatic build system (Maven proposal will help to do automatic build).
  * Where to annouce stable/"unstable" release ?
- * Where to release stable/"unstable" release ? Separate folders ?
+ * Where to release stable/"unstable" release ?
  * What's an "unstable" release ? alpha release ?
  * When is "unstable" release made ?
@@ -37 +37 @@
  * Final Release is built two weeks after RC2
  * Stable releases are published in the main "!GeoNetwork_opensource" folder in sourceforge
- * Stable releases are annouced on user and devel mailing lists
+ * Stable releases are announced on user and devel mailing lists
 
 The Project Steering Committee (PSC) can postpone a stable release by vote on the mailing list.
@@ -46 +46 @@
  * Alpha releases are created on a feature based strategy : after major proposals have been added to trunk
  * Alpha releases are based on trunk and are built with uneven version numbers
- * Alpha releases are published in the "Alpha_GeoNetwork_opensource" folder
- * Alpha releases are annouced on devel mailing lists only
+ * Alpha releases are published in the "!GeoNetwork_opensource_alpha" folder
+ * Alpha releases are announced on devel mailing lists only
 
 Fixes are committed to both trunk and even numbered branch