Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] CVS support plugin discontinuation - SimRel build changes needed


I think you are barking up a tree that is no longer occupied by a cat. 

It's fine to make cross-project aware of the issue, but I think everything meaningful to be said on the topic has now been said, with Stephan Hermann's summary being particularly savvy...

If you think more needs to be said and you think that what you say will actually sway the very people who you think should take some form of action (which I feel makes you overly optimistic), it would be best, to do so on the issue that you've already opened where anyone/everyone interested in further discussions can participate too:

My sense is that this decision was made long ago and that no one is obligated to make an older version of CVS continue to work in current or future releases.


On 04.01.2023 09:48, Ed Willink wrote:

On 03/01/2023 21:13, Stephan Herrmann wrote:
* The code change in question didn't touch any true API.

IMHO, UX is also API, albeit spelling changes / menu rationalization / form prettifying are acceptable and sometimes desirable. The fundamental user capability to check out a CVS project is API.

Presumably it was possible to write a program that re-used team CVS support to check out a CVS project. The API used by this hypothetical program is now broken. If such a program was only possible using internal classes, then those classes constitute what I call artificially internal functionality; internal classes that, in the absence of a suitable Facade, users have no alternative but to use for reasonable purposes.


        Ed Willink

cross-project-issues-dev mailing list
To unsubscribe from this list, visit

Back to the top