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?
Thoughts?
Cheers,
Dave
------------------------------------------------------------
This email and any attachments are intended only for the named
recipient and may contain confidential and/or privileged material.
Any unauthorized copying, dissemination or other use by a person
other than the named recipient of this communication is prohibited.
If you received this in error or are not named as a recipient,
please notify the sender and destroy all copies of this email
immediately.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2321524
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-20 07:02:03 CEST