Context Navigation

Changes between Version 1 and Version 2 of Ticket #29917, comment 14

v1	v2
3	3	That’s not what I’m saying. What I’m saying is that we can’t just change a design decision in a bug fix. Not when there’s a one line change that just fixes it.
4	4
5		We can change the feature if decided, but that would be done separately: the policy is that to change a design there needs to be a discussion and agreement on django-developers and so on. (The use-case that we’re proposing to break is kind oif useful: declare an action on a base class and not have to redeclare it later: it’ll just be there. That was one of the original considerations.)
	5	We can change the feature if decided, but that would be done separately: the policy is that to change a design there needs to be a discussion and agreement on django-developers and so on. (The use-case that we’re proposing to break is kind of useful: declare an action on a base class and not have to redeclare it later: it’ll just be there. That was one of the original considerations.)
6	6
7	7	The impressive list of people is relevant because they obviously discussed this at length and spent a lot of time putting the feature together. It’s been unchanged for 10 years. They must have got something right.