tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Tapestry Wiki] Trivial Update of "Tapestry41Roadmap" by BobHarner
Date Sun, 02 Jan 2011 21:04:45 GMT
Dear Wiki user,

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

The "Tapestry41Roadmap" page has been changed by BobHarner.
The comment on this change is: outdated note.
http://wiki.apache.org/tapestry/Tapestry41Roadmap?action=diff&rev1=21&rev2=22

--------------------------------------------------

+ || NOTE: This is outdated information that applies only to Tapestry 4.1.  For the current
Tapestry roadmap see [[http://tapestry.apache.org/introduction.html#Introduction-Roadmap]]
||
+ 
  = Process Changes =
  
  Tapestry 4.0 had a very (too) long release cycle. New committers came (and, unfortunately,
went) and the frayed edges of the process became
- maniftest towards the end of the  cycle.
+ manifest towards the end of the  cycle.
  
  == Release Numbering ==
- Tapestry 4.0's release cycle has clearly shown the limitations of Tapestry's release numbering
system. Other projects have benefitted from
+ Tapestry 4.0's release cycle has clearly shown the limitations of Tapestry's release numbering
system. Other projects have benefited from
  a numbering scheme that doesn't not explicitly identify alpha/beta/rc status, since that
status is voted upon after the release has been produced.
  
  To merge into the Apache and Open Source mainstream, Tapestry numbering shall change; the
first 4.1 release will be 4.1.1 (not 4.1-alpha-1).  Once the code changes are reasonably stable,
an existing release will be voted in as the first beta release (it may be, say, 4.1.7).  Further
beta releases will follow. Eventually a stable beta release  can be voted as the final 4.1
release (say, 4.1.12).
@@ -14, +16 @@

  == Build Environment ==
  
  Tapestry 4.0's home grown, Ant based build environment has been a growing issue. While lean,
and mean, it is too difficult for end users to set up,
- and typically required the users download the source to HiveMind and Forrest as well.  Currently
(Jan 2006), HiveMind 1.2 is being converted to bulid using Maven 2.0. Once that is succesful,
a conversion of Tapestry to Maven 2.0 will occur as well.
+ and typically required the users download the source to HiveMind and Forrest as well.  Currently
(Jan 2006), HiveMind 1.2 is being converted to build using Maven 2.0. Once that is successful,
a conversion of Tapestry to Maven 2.0 will occur as well.
  
  Having an easily built framework will reduce the need for frequent releases, as it will
be a simple, standard process for anyone to download latest source from Subversion and build
locally.
  

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message