Context Navigation

Changes between Initial Version and Version 1 of Ticket #11985, comment 2

initial	v1
2	2	> Given the number of Option changes that are already made for milestone:1.2, it seems best to make these changes before that release.
3	3
4		Considering the use-case of a deployment script that installs a Trac instance and sets ~~a number of configuration options~~, the changes in tickets such as #11776 could be considered API changes. I'm not sure it's worth retaining the old option names and having some deprecation mechanism for renamed options, however considering that these changes may be viewed as API changes would provide more motivation for completing further changes before Trac 1.2 so that end-users only have to deal with a large number of changes in a single major release.
	4	Considering the use-case of a deployment script that installs a Trac instance and sets configuration options using TracAdmin, the changes in tickets such as #11776 could be considered API changes. I'm not sure it's worth retaining the old option names and having some deprecation mechanism for renamed options, however considering that these changes may be viewed as API changes would provide more motivation for completing further changes before Trac 1.2 so that end-users only have to deal with a large number of changes in a single major release.