Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update roadmap page #19

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

update roadmap page #19

wants to merge 1 commit into from

Conversation

kinkie
Copy link
Contributor

@kinkie kinkie commented Jan 17, 2024

No description provided.

@kinkie kinkie requested review from rousskov and yadij January 17, 2024 11:10
Copy link
Contributor

@rousskov rousskov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Squid 7" section of this RoadMap page has pretty much nothing to do with the "road map" concept. It poorly duplicates information already available elsewhere (change log, release notes, Bugzilla, etc.). It will be virtually always stale/inaccurate at least until we stop updating the corresponding Squid code (at which point the section will become pretty much irrelevant).

I recommend deleting this entire page.

If others insist on keeping Squid v6 info (that naturally suffers from very similar problems!), then we can mark this page as obsolete instead (so that we do not have to maintain it and have a better chance of removing it later when it becomes even more obvious that v6 info does not belong to RoadMap (and is available in a better shape elsewhere)).

Links or simplified forms producing bug lists like "bugs affecting version X" and "bugs introduced in version Y" may be useful. Ideally they should be added n our Bugzilla site itself, where folks (should) expect to find information about bugs.

@yadij
Copy link
Contributor

yadij commented Jan 18, 2024

FTR; Under MoinMoin this section was auto-included from the page tracking release features prior to release-notes final edit. The conversion to github somehow made it duplicate text.

This is one of the pages which are used as reference by vendors and others. So dropping is not reasonable despite how much overhaul of the policies mentioned within need to be done by the Board.

For this PR I would like to see the wiki auto-includes restored, the release-specific page is due for maintainer updates in Feb. That should be "good enough" for this PR scope.

@rousskov
Copy link
Contributor

This is one of the pages which are used as reference by vendors and others. So dropping is not reasonable

I do not understand why removing duplicated and misplaced information (that is easily found elsewhere) is "not reasonable" even if it is "used as reference". Surely, "vendors and others" can adjust (and will benefit from this improvement in the long run).

Needless to say, we can leave a short temporary note directing readers to the right sources of information. This PR can do that if we have good reasons to suspect that such a temporary note is needed (i.e. that "vendors and others" will not be able to quickly find the necessary information without such a note).

For this PR I would like to see the wiki auto-includes restored, the release-specific page is due for maintainer updates in Feb.

The suggested changes sound like a waste of precious human resources to me, but I will not block a PR that correctly duplicates information if others insist on that duplication.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants