From: david noble [mailto:david.noble_at_icbc.com]
Sent: Wednesday, May 20, 2009 12:18 AM
To: users_at_subversion.tigris.org
Subject: Roadmap for Subversion?
Hi All,
Looking for a roadmap document for where Subversion is going past 1.6.2,
ideally for the next 2 major versions at least.
Is Configuration Management going to be a large part of where SVN is
going? And if it is, will it be focused on "pure" config mgmt (ie
setting up dev/test/QA/prod'n environments for things like
hardware/network/server/client configs, M/F code, and .NET/J2EE - ie
everything an app depends on) or will it move into areas such as dynamic
monitoring of the production environment a la Radia (now HP Openview
CMDB). Gartner also criticises SVN for its lack of Production Support
features such as tracing bugs back to source code and team-based
development (for IT shops where there are say 100+ developers). How will
SVN address this? Will it ever address this?
I'm sure Gartner says "spend the money on Microsoft's TFS".
My thoughts:
* Why would any VCS want to know about J2EE/.NET or any other
particular technology? The moment you put tech-specific artefacts in,
you've suddenly limited yourself with regard to un-supported
technologies. (and even if you think you'll never ever support anything
other than <latest tech> something new will come along.
* Why would any VCS support setting up your production
environment? For hardware?! It's supposed to control your application
sources so you don't lose them, not to install your OS, dev tools,
libraries, and hardware drivers for you.
I'm not sure you haven't confused SVN with some other kind of tool.
Anyway, there is a published roadmap:
http://subversion.tigris.org/roadmap.html
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2327187
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-20 10:32:14 CEST