Gary, IMO, the short answer is focus on targeting 1.6.
I can express my and @mire's opinion on DSpace 2.0 timeline and the previous years funded development effort. The largest lesson I think we learned from last years 2.0 development initiative is that we need to work on the individual features of DSpace 2.0 in tractable smaller projects that will take the whole community from DSpace 1.x to the DSpace 2.x platform. My recent work this last fall on the 2.0 technology base was a "consolidation effort". Working to bring some of the major accomplishments of the 2.0 work into a state that they would have more short term benefit to the whole community. There are still significant pieces of the 2.0 funded development iteration that need to be merged into the 1.x codebase to have them also be of benefit. Those items we outlined in my DSpace Services presentation at the fall 2009 DSUG meeting in Sweden. http://www.slideshare.net/mdiggory/dsug09-services-2255693 http://www.slideshare.net/mdiggory/dsug-2009-dspace-statistics-contribution It is important that we work to establish an iterative process that allows us to outline migration "steps" that will carry the community along this process. As such, we need to consider that 1.x is not obsolete, but instead represents the active heart of our development communities efforts (and it the focal point where any 2.0 development will need to be merged in the future). This is made obvious by the healthy growth in community activity in its maintenance and upkeep that has occured in the last couple years. Targeting your work within this community is your "best" possible path to success on your project, it is here that the largest knowledge-base of support exists and where any work you may be interested in contributing would be of greatest benefit. I hope this brief outline is helpful to you. Cheers, Mark On Sun, Jan 10, 2010 at 6:55 AM, Gary Kopp <[email protected]> wrote: > I would like to use DSpace as the foundation of an internal document > management system, which I will integrate with various other functions. I am > a J2EE programmer and not afraid to get my hands dirty. I'm confused about > the status of DSpace version 2. I assume version 2 represents the "new > architecture" I've seen referenced elsewhere. I'd hate to start my work with > an obsolescent verson (1.5/1.6) if I can avoid it. But I see a lot of > ongoing work on 1.5/1.6 suggesting that these versions are undergoing active > enhancement and might represent a relatively stable target for my purposes. > But my work might be somewhat wasted when version 2 hits the streets. Early > releases of version 2 seem to be available, and see I some work going on > there. Is there enough in version 2 now to make it a possible starting point > for a new DSpace deployment, even in beta form, or is it just too early for > that? BTW, I didn't find a roadmap anywhere, which may just mean I didn't > look in the right place. > > --Gary Kopp -- Mark R. Diggory Head of U.S. Operations - @mire http://www.atmire.com - Institutional Repository Solutions http://www.togather.eu - Before getting together, get t...@ther ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
