Dear Wiki user,

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

The following page has been changed by JesseKuhnert:
http://wiki.apache.org/tapestry/BoardReportOctober2007

------------------------------------------------------------------------------
  
  It is expected that Tapestry 4 development will continue for some time but 
mostly be concentrated around minor improvements and bug fixes - until more of 
the core T4 developers have had time to transition over to Tapestry 5.  (the 
Ajax features being finalized will probably help this process)
  
- === OGNL ===
+ ==== OGNL ====
  
  The OGNL release cycle has now more or less started to mirror the Tapestry 4 
release cycle,  so the same sorts of things have been happening there as in 
Tapestry 4.  Tons of bug fixes / performance improvements and the addition of 
java 5 support (besides one varargs bug) have also silently made their way in 
to the last 2.7.1 release of OGNL. 
  
@@ -23, +23 @@

  
  Tapestry 5 progress is still a bit slow, but has picked up just in the last 
couple of weeks, and is expected to return to a reasonably brisk pace shortly.  
However, the road map has been extended out as the Ajax features are still 
missing (partly from debate over which Ajax framework to embrace).
  
+ == New Snapshot build / documentation process ==
  
- Nightly builds (via a Maven snapshot repository) and documentation (at 
http://tapestry.formos.com/nightly/tapestry5) are now available for Tapestry 5.
+ Nightly builds (via a Maven snapshot repository) and documentation (at 
http://tapestry.formos.com/nightly/tapestry5) are now available for Tapestry 5. 
 It is expected that Tapestry 4 will also eventually use this resource to 
publish snapshot versions of both software and documentation to keep the core 
Apache site static and in line with the latest stable releases.
  

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

Reply via email to