Don, Has anyone decide how to release separate libraries for 1.3? I ask this because presumably 2.0 would follow something similar, having multiple releases per components.
Paul --- Don Brown <[EMAIL PROTECTED]> wrote: > Thank you everyone for all the constructive input into the WebWork 2 > incubation process. With > your continued support > and assistance, we should be out of Incubation quicker than expected and be > on our way to the > first Struts Action 2 > release. I'm enjoying seeing how developers from both projects are coming > together to form a > unified Action 2 team. > > It was suggested to send out a weekly status message, keeping everyone > abreast of where WebWork > 2 stands in the > Incubation process. Since we already have a STATUS.txt file [1], which I > encourage everyone to > follow, I'll just > highlight a few outstanding tasks that we are looking for volunteers on or > issues that need > discussing. > > - The Pico code is under the Pico copyright. I believe we'll need them to > submit a software > grant [2]. Anyone > willing to take that on? > > - The Dojo component package was previously 'webwork'. I've temporarily > renamed it to > 'struts', but that might > conflict with Shale if they create new Dojo components. Or perhaps that > might be a good thing? > > - Migration, migration, migration. Some of you have asked me off list what > you can do to > help. The biggest thing we > need is Struts users to try WebWork and take notes on what worked, what > didn't, and pitfalls can > be avoided. Ted has > started collecting a list of best practices [3]. We also have a wiki page > [4], which allows any > Struts user to record > their tips, experiences, and recommendations for new migration tools. Please > join in and help > shape the approach and > content of the Struts Action 2 migration story. > > - The build now builds struts-action-2.0-dev.jar, which can be placed into > your sandboxes for > testing and getting > acquainted with Struts Action 2. With most of the renaming completed, the > files, code, and > configuration naming should > be stable enough to start working with it. The WebWork 2 project had a > continuous integration > server for automated > builds and testing. It would be valuable to have that service, even while in > the Incubator. > What about setting up a > temporary build server either in an Apache zone or on a developer's computer? > > I don't know about a weekly message, but I'll try to get something out > somewhere close to that. > Keep up the good work! > > Don > > [1] http://svn.apache.org/viewcvs.cgi/incubator/webwork2/STATUS.txt > [2] http://www.apache.org/licenses/software-grant.txt > [3] > https://svn.apache.org/repos/asf/struts/sandbox/trunk/action2/PRACTICES.txt > [4] http://wiki.apache.org/struts/StrutsAction2 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
