Dear Users,

1. A bug was found in init.n to make $Line function out of order. Its definition used to be

($Line=x_Real)^:=Module[{`n=Max[0,x]},
Unprotect[$Line,Out];
Do[Out[`i]=.;MessageList[i]=.,{i,n+1,$Line}];
$Line:=Evaluate[`n];
Protect[$Line,Out];
x];
Protect[$Line,Out];

which was OK when System`i is not defined before this, but some newly inserted lines actually use that, so $Line became broken. Then it is rewritten in the new version as

($Line=x_Real)^:=Module[{`n=Max[0,x]},
Unprotect[$Line,Out];
Do[Out[`i]=.;MessageList[`i]=.,{`i,n+1,$Line}];
$Line:=Evaluate[`n];
Protect[$Line,Out];
x];
Protect[$Line,Out];

Dear Users,

1. A bug was found in OpticsPlot when plotting a list like

data={{1,0.5e-3,0.1e-3},{1.5,0.4e-3,0.1e-3}};
g1=OpticsPlot[{{"BX","BY"},{"SIGX","SIGY",{data,Unit->Meter}}},ListCoordinate->"S"];

where data contains error bars.

Dear Users,

1. A very very old bug was found in matching LENG, GX, and GY. It is too old and not able to track, probably more than 10 years. The evaluation of the difference between these functions and the goals were wrongly treated as CHI1, CHI2, CHI3, so that the only their modulo were used as the difference.
Then the difference was zero when it is (2n+1)Pi. In most cases they still could be matched, unless it falls into such points.