Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
added a commit
Mar 16, 2018
@ewg118 Yes it is in 2017.2.1 PE. On the right hand of the issue, you can see what "project" has been assigned to the issue: for this particular issue, you can see that it has been assigned to the 2017.2.1 and 2018.1 "projects", which (unless we made a mistake!), means it will be in the corresponding builds.