<p dir="auto">What is the correct process to update typings for the "master" and the “types-2.0” branch:</p>
<p dir="auto">This project has a “master” branch, and a “types-2.0” branch.</p>
<p dir="auto">What is the correct process to make a change to a typings file  ?<br>
1]<br>
First create the fix as a PR in the “master” branch and then duplicate the code changes in a new PR on the ”types-2.0″ branch ?</p>
<p dir="auto">2]<br>
Or create a PR in the “master” branch and also create a PR on the “types-2.0” branch which does a merge ?</p>
<p dir="auto">3]<br>
Or ?</p>
<p dir="auto">I could not find this information on the Wiki yet ? Maybe an idea to add something here about the process?</p>
<p dir="auto">See also my question here : <a href="https://blogs.msdn.microsoft.com/typescript/2016/06/15/the-future-of-declaration-files/#comment-25535" rel="nofollow">https://blogs.msdn.microsoft.com/typescript/2016/06/15/the-future-of-declaration-files/#comment-25535</a></p>
<p dir="auto">I propose a simple naming convention for issues that relate to an individual type definition.</p>
<p dir="auto">If I want to file a bug about the jQuery definition, I would name my issue</p>
<blockquote>
<p dir="auto">[jquery] missing method "foo"</p>
</blockquote>
<p dir="auto">The text within square brackets must match the name of the typing's directory in this repository.</p>
<p dir="auto">The motivation is that, when I discover a bug in a type definition, I want to make sure I don't file a duplicate bug.  Therefore I need to search the issue queue for any other issues related to that type definition.</p>
<p dir="auto">If this naming convention is explained on definitelytyped.org's <a href="http://definitelytyped.org/guides/contributing.html" rel="nofollow">contribution guide</a>, we can easily link to it when someone makes an issue that doesn't follow the convention.  Before long all issues will use the convention, and we'll no longer need to explain it.  That's the theory, at least.</p>