Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Use valid version in maintainer guide #13175

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

Merged
merged 1 commit into from
Feb 19, 2020

Conversation

OskarStark
Copy link
Contributor

No description provided.

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Copy link
Member

@javiereguiluz javiereguiluz left a comment

Choose a reason for hiding this comment

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

I like this attention to detail ... but this document is for internal use only, so it's not critical to keep it updated like this. In any case, thanks for this contribution Oskar.

@@ -195,7 +195,7 @@ Step 3: Merge it into the other branches

If a PR has not been merged in ``master``, you must merge it up into all the
maintained branches until ``master``. Imagine that you are merging a PR against
``3.4`` and the maintained branches are ``3.4``, ``4.2`` and ``master``:
``3.4`` and the maintained branches are ``3.4``, ``4.4`` and ``master``:
Copy link
Contributor

Choose a reason for hiding this comment

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

I would add 5.0 though

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I do this while upmerging 👍🏻

OskarStark added a commit that referenced this pull request Feb 19, 2020
This PR was merged into the 3.4 branch.

Discussion
----------

Use valid version in maintainer guide

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/roadmap for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `master` for features of unreleased versions).

-->

Commits
-------

2a596de Use valid version in maintainer guide
@OskarStark OskarStark merged commit 2a596de into symfony:3.4 Feb 19, 2020
@OskarStark OskarStark deleted the update-maintainer-guide branch February 19, 2020 06:53
OskarStark added a commit that referenced this pull request Feb 19, 2020
* 4.4:
  Update http_authentication.rst
  Update routing.rst
  Update routing.rst
  Update mailer.rst
  Update messenger.rst
  Reference method
  Update form.rst
  Use valid versionj in maintainer guide. refs #13175
  [DependencyInjection] Fixed public service use case
  fixup
  tweak #13099
  Use valid version in maintainer guide
  Mention region parameter for Mailgun mailer too
  Update service_subscribers_locators.rst
OskarStark added a commit that referenced this pull request Feb 19, 2020
* 5.0:
  Update http_authentication.rst
  Update routing.rst
  Update routing.rst
  Update mailer.rst
  Update messenger.rst
  Reference method
  Update form.rst
  Use valid versionj in maintainer guide. refs #13175
  [DependencyInjection] Fixed public service use case
  Use valid version in maintainer guide
  Mention region parameter for Mailgun mailer too
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.