The development cycle within most Apache products, and most open source products at large, is that volunteers are coding in either "evolutionary" mode or "revolutionary" mode. (The same is often true of closed-source product too.)
Right now, Struts 1.x is considered to be in "evolutionary" mode. Changes to the code base are expected to happen step-by-step, with backward compatibility as a mandatory feature. Over the years, we have recognized that, if we-knew-then what we-know-now, there are several things we would have done differently with Struts 1.x. To give people a chance to try create a new Struts architecture, that is not chained to the past, we have dubbed Struts 2.x as a "revolution". This means that the code base will start as a clean slate, and backward compatibility is not a "mandatory" feature. (Though, obviously, a high degree of compatibility with Struts 1.x would be desirable.) Of course, anything can be said. In a volunteer environment, all that really matters is what people do. Nothing in a volunteer project is really decided until someone "shows us the code". Before starting anything new in a team-based environment, it's usually helpful to put together some type of proposal, describing what you have in mind. Jericho is a proposal describing some of the ideas people have broached for Struts 2.x. The next stage would be to post some working code in CVS, creating a working "whiteboard" with code that people can take for a spin. If the whiteboard grows into something useful, then someone might suggest we release it as a Struts product. At that time, it would be given a true product name and a release number. Until then, the popular convention is to give the proposal/whiteboard some type of code name. In this case, the codename is Jericho. http://cvs.apache.org/viewcvs.cgi/jakarta-struts/contrib/struts-jericho/ Of course, the fact that some of us may be working on a Struts 2.x whiteboard doesn't affect what other people can do in regard to the Struts 1.x distributions. Several lines of development can proceed independently and at their own pace. It all depends on what itches volunteers need to scratch. -Ted. On Sat, 15 May 2004 22:37:29 +0800, Andrew Hill wrote: > <snip> > Meanwhile, as part of a writing assignment, I'm working on a new > controller design based on Commons Chain, which might become the > first code commit toward the development of Struts-Jericho. Of > course, whether Jericho ever becomes Struts 2.x remains to be seen. > </snip> > > Hi Ted, > > > What is this "Jericho" Ive been seeing occasional references to and > how does it relate to the normal Struts development process? > > -Andrew > > > -----Original Message----- > From: Ted Husted [mailto:[EMAIL PROTECTED] > Sent: Saturday, 15 May 2004 22:30 > To: Struts Developers List > Subject: Re: struts future plans > > > On Sat, 15 May 2004 06:34:03 -0500, Vic Cekvenich wrote: > >> what are the plans for struts? >> >> >> should you add active developers interested in keeping up? >> > > Most of the future plans are on the roadmap. Once a stable Commons- > Validator release is available, we can cut 1.2.1 and then bring > Struts-Chain down from contrib, to kickoff the 1.3.x series. > > We have invited Niall Pemberton to join us as a Struts Committer, > and he has accepted. We're just waiting for root to sent up his > account before making a formal announcement. > > Don Brown has also just submitted a proposal to the Struts PMC > regarding the creation of Struts-BSF and Struts-Scripting > subprojects, based on code already available at struts.sf.net. The > votes were positive, and we should be announcing that here as soon > as Don is ready to commit the code. > > As a top-level project, we are now conducting some of the > "management" business on the PMC list, such as nomination of new > committers and proposals for new subprojects. But all the coding > discussions and planning do take place here and no where else. That > much will never change. > > But, right now, coding is at an impasse pending the release of a > stable Commons Validator component. I started to move that along > myself, there is just too much on my plate right now, and I had to > let it go. > > Meanwhile, as part of a writing assignment, I'm working on a new > controller design based on Commons Chain, which might become the > first code commit toward the development of Struts-Jericho. Of > course, whether Jericho ever becomes Struts 2.x remains to be seen. > > -Ted. > > > -------------------------------------------------------------------- > - To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > > > -------------------------------------------------------------------- > - To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
