About exactly 1 year ago the plans for 2.0 were set forth and agreed upon in a very large IRC meeting. Attendees included Hani, Rickard, Jason, Matt Baldree, and many other prominent people involved with WebWork. Those plans have been delivered with the release of 2.0, as per the roadmap we laid forth.
I believe that the 1.x and 2.x lines are different in terms of implementation, but not in what they do or their APIs (JSP tags, interfaces, etc). That is enough justification that no name change is necessary. The only thing that will propagate this identity crisis is if a majority of 1.x users are truly unwilling to make the migration to 2.x. If that is the case, I agree, it is pointless to give both products the same name. I think the right thing to do, as Hani has said, is to _maintain_ 1.x. By maintain, I would assume this means continuing to provide support, documentation, bug fixes, and minor enhancements. It is important that any chance in 1.x is brought to the 2.0 developer's attention so that we can make the user experience of migrating from 1.x to 2.0 as painless as possible. I would be curious to hear from other 1.x users besides Hani what their thoughts are on this issue. I invite anyone that uses 1.x to please email me (or the list) with your thoughts so that I can get a better idea as how to maintain these two very different code lines. I also want to make it clear to Hani that no one is expecting you to migrate from 1.x to 2.0 in your code. That is entirely up to you and your development team. Likewise, no one expects you to not patch 1.x when a bug or request comes up, as "upgrade to 2.0" is NOT a realistic answer for everything. However, I want to make it clear that, for the sake of users like Wayland that are seeing a bit of an identity crisis, WebWork 2.x is where all major enhancements and features will be built. It would be irresponsible to both the 1.x and 2.x users to let the branches continue to diverge any more than they already have. Is that agreeable? Patrick > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Hani Suleiman > Sent: Sunday, February 08, 2004 9:50 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Intended roadmap for webwork project? > > No merge will happen. > > There's a demand for 1.x to keep being maintained. A not insignificant > number of people use this in production environments and work with it > on a daily basis (I suspect more than ww2 currently). Many of these > people are reluctant to migrate to ww2 (for now at least). > > If/when at some point in the future we (and by we, I meant some > majority of ww1 users) feel that ww2 is ready for prime time, 'we' > might migrate. > > On Feb 9, 2004, at 12:46 AM, Wayland Chan wrote: > > > Hello, > > > > I'd like to ask the core team what their intentions are for the > > webwork platform. It confuses me greatly > > that we have two distinctly different frameworks, maintained by two > > completely differently teams, using > > essentially the same name, and basically doing the same thing. > > > > Do you guys intend on merging the two versions into one product? > > > > If not, then let's just call it as it is and rename the WW2 to > > something else. > > > > > > > > Wayland Chan > > email: wchanATtrekspaceDOTcom > > > > ---------------------------------------------------------- > > Get your free email account from http://www.trekspace.com > > Your Internet Virtual Desktop! > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by EclipseCon 2004 > > Premiere Conference on Open Tools Development and Integration > > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > > http://www.eclipsecon.org/osdn > > _______________________________________________ > > Opensymphony-webwork mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
