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

Any comment about upcoming Git Rev News edition 112 #714

Closed
chriscool opened this issue Jun 1, 2024 · 13 comments
Closed

Any comment about upcoming Git Rev News edition 112 #714

chriscool opened this issue Jun 1, 2024 · 13 comments

Comments

@chriscool
Copy link
Collaborator

A currently mostly empty draft is there:

https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-112.md

Feel free to comment in this issue, suggest topics, suggest persons to interview, or use the edit button (that looks like a pen) to edit and create a pull request with the changes you would like.

Let's try to publish this edition around the end of June 2024!

Thanks!

cc @jnareb @mjaix @sivaraam @gitster @stepnem

@chriscool
Copy link
Collaborator Author

In the issue for the previous edition @jnareb suggested:

The following discussion might be of interest (if it will take more shape before publishing this edition):

[RFC PATCH] docs: document upcoming breaking changes

@chriscool
Copy link
Collaborator Author

@davvid
Copy link
Contributor

davvid commented Jun 30, 2024

Garden and Git Cola both had a feature release. These should be in the version check script so it might just need a rerun to refresh.

@chriscool
Copy link
Collaborator Author

@davvid right, thanks! This should be fixed now.

@jnareb
Copy link
Member

jnareb commented Jun 30, 2024

My links have been added in e8bc2b9 (including one LWN.net SubscriberLink).

@bpugh
Copy link
Contributor

bpugh commented Jul 1, 2024

Hi all,
I look forward to reading the newsletter every month and thought I'd take a peek at the upcoming issue and the link "Pull Request vs Merge Request" caught my eye so I clicked on it but after reading it I wonder whether it actually adds any value or might even confuse some people.

At best, it seems like an unnecessarily long way to say the only real difference is the terminology that Github and Gitlab use.
But I think it's also confusing since they have two different sections where they describe the "workflow" of each but they are basically the same just reworded enough to look like slightly different processes.

Towards the end they also mention "Beyond terminology, there might be slight variations in functionalities depending on the platform. GitLab offers features like:" and they list:

  • Merge conflict detection
  • Approval rules

But this implies that Github doesn't offer these features when in fact they do.

I don't think there's anything wrong with plugging a product at the end of a post but it didn't feel like they really tried to write a useful post.
Maybe it's just me and I'm being too critical, but to me it comes across as them just trying to meet some content quota to drive SEO for their product.
I totally understand if you all think it's still worthwhile to include in the newsletter but I just thought I should mention my concern.

Thanks and I appreciate all the work you all do in putting together the newsletter!

@chriscool
Copy link
Collaborator Author

@jnareb thanks for the great links!

@bpugh thanks for your opinion on that link! @jnareb will decide about keeping the link or not.

@mjaix
Copy link
Contributor

mjaix commented Jul 1, 2024 via email

@chriscool
Copy link
Collaborator Author

Hi @mjaix, no worries. 13:00 CET is OK for me.

@jnareb
Copy link
Member

jnareb commented Jul 1, 2024

@bpugh thanks for your comment. I have removed the "Pull Request vs. Merge Request: Essential Differences" article (5bbbcd4).

@mjaix
Copy link
Contributor

mjaix commented Jul 1, 2024 via email

@chriscool
Copy link
Collaborator Author

@mjaix your changes look great, thanks!

@chriscool
Copy link
Collaborator Author

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

No branches or pull requests

5 participants