Next week we plan to begin publishing from master and ditch the types-2.0 branch. So we will do:
master PRs. (remaining)types-publisher temporarily.master to types-2.0.types-2.0 to master.types-publisher back on, this time publishing from master.master?Not yet. We're clearing out pull requests for master.
types-2.0?Yes. After we switch to using master, we'll do regular merges from types-2.0 to master.
But, once the merge has happened (you'll know because this issue is closed), you should prefer to make new pull requests to master.
@andy-ms , in light of https://github.com/Microsoft/types-publisher/issues/214#issuecomment-266056954, do you think we could discuss having types-publisher publish from "stable" and allowing changes for things like Typescript 2.1 go to master? OR to create a types-2.1?
See the next comment (https://github.com/Microsoft/types-publisher/issues/214#issuecomment-266126733); we'd like to have just one branch.
//CC @blakeembrey, @alexeagle, @vvakame, @johnnyreilly, @staxmanade,@Diullei, @RyanCavanaugh and @DanielRosenwasser
Thanks for the heads up @mhegazy
It's all done. We will accept (and prefer) pull requests to master now.
have the changes for adding autoHide and endDate to Jqueryui/index.d.ts been committed and merged with Master ?
@Mukesh1303 yes.
Why not delete the types-2.0 branch? (and some other old branches)
We have to clear out all the PRs still targeting it first.
Deleted the types-2.0 branch.
@andy-ms @types/callsite is still pointing to types-2.0 in it's package description.
I assume just triggering a new publish would resolve that? Can that be done w/o making an actual change to the package?
Most helpful comment
Deleted the
types-2.0branch.