[DISCUSS] Next steps for 2.3/2.4 ...
"Howard M. Lewis Ship" <[email protected]> Thu, 9 Jan 2003 19:00:03 -0500
| Newsgroups | gmane.comp.java.tapestry.contrib |
|---|---|
| Message-ID | <005101c2b83b$3a187da0$3dc41e42@howardczkz2sl3> |
This is a multi-part message in MIME format. ------=_NextPart_000_004E_01C2B811.510852D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I would like to get 2.3 put to bed (yes, you've heard this before). I haven't looked at the 2.3 code in a bit; I believe Malcolm put in a = "globals" property on IEngine. Maybe there was some work on the = contrib:PopupLink component? And we'll check the documentation. I would like to create a branch for 2.3 so that we can fold my changes = and MB's changes into HEAD. In a worst-case scenario, changes to 2.3 = would have to be done in a branch and in HEAD. Once we merge everything together and get it stabilized, we can see = what's next ... probably renaming packages from net.sf.tapestry to = org.apache.tapestry, then maybe a 2.4-alpha-2. We can also see what it = takes to get automated builds going, and see about redoing the web site = to fit into the Apache look and feel. Lot's and lots to do. Don't forget to get feedback to Neil on the new Tutorial. Other ideas: Rename the JAR from "net.sf.tapestry-x.x.x.jar" to simply = "tapestry-x-x-x.jar". Something similar for contrib. Probably want to work on build.xml to generate distros that are more = like other Apache products. A -bin distro contains the precompiled JARs and all the documentation. A -src distro contains what? A superset of -bin, with source code? = Typically, it's a snapshot of the workspace, does it have to be? I = really like distributing the source code packaged as a .jar, ready for = linkage in Eclpise. Start getting used to Apache Bugzilla. Manually (?) move bugs and = feature requests over to Bugzilla from SF. Mailing lists ... when do we start to shift over to Jakarta/Apache = mailing lists? Yep, lot's to do. ---- Howard Lewis Ship [email protected] http://tapestry.sf.net ------=_NextPart_000_004E_01C2B811.510852D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2719.2200" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>I would like to get 2.3 put to bed = (yes, you've=20 heard this before).</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I haven't looked at the 2.3 code in a = bit; I=20 believe Malcolm put in a "globals" property on IEngine. Maybe = there was=20 some work on the contrib:PopupLink component? And we'll check the=20 documentation.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I would like to create a branch for 2.3 = so that we=20 can fold my changes and MB's changes into HEAD. In a worst-case = scenario,=20 changes to 2.3 would have to be done in a branch and in = HEAD.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Once we merge everything together and = get it=20 stabilized, we can see what's next ... probably renaming packages from=20 net.sf.tapestry to org.apache.tapestry, then maybe a 2.4-alpha-2. = We can=20 also see what it takes to get automated builds going, and see about = redoing the=20 web site to fit into the Apache look and feel. Lot's and lots to=20 do.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Don't forget to get feedback to Neil on = the new=20 Tutorial.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Other ideas:</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Rename the JAR from = "net.sf.tapestry-x.x.x.jar" to=20 simply "tapestry-x-x-x.jar". Something similar for = contrib.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Probably want to work on build.xml to = generate=20 distros that are more like other Apache products.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>A -bin distro contains the precompiled = JARs and all=20 the documentation.</FONT></DIV> <DIV><FONT face=3DArial size=3D2>A -src distro contains what? A = superset of=20 -bin, with source code? Typically, it's a snapshot of the = workspace, does=20 it have to be? I really like distributing the source code packaged = as a=20 .jar, ready for linkage in Eclpise.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Start getting used to Apache = Bugzilla. =20 Manually (?) move bugs and feature requests over to Bugzilla from=20 SF.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Mailing lists ... when do we start to = shift over to=20 Jakarta/Apache mailing lists?</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Yep, lot's to do.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>----<BR>Howard Lewis Ship<BR><A=20 href=3D"mailto:[email protected]">[email protected]</A><BR><A=20 href=3D"http://tapestry.sf.net">http://tapestry.sf.net</A><BR></FONT></DI= V></BODY></HTML> ------=_NextPart_000_004E_01C2B811.510852D0-- ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com