Re: [patch,6.0,rfc,rfa:doco] Finish "mi2"/"mi3" rollover

["Eli Zaretskii" <eliz at elta dot co dot il>]

> Date: Mon, 04 Aug 2003 15:41:28 -0400
> From: Andrew Cagney <ac131313@redhat.com>
> 
> This finishes the mi1/mi2/mi3 rollover.  It also fixes a bug.  The=20
> previous changes forgot to register "mi2", and set "mi" to "mi3".=20
> Anyway it:
> 
> - adds "mi2" and "mi3"
> - makes "mi" select "mi2" the last released "mi" version.
> - updates the doco to mention that "mi2" was released in GDB 6.0
> - rolls the testsuite so that there is a frozen mi2-*.exp
> 
> Note that "mi" is selecting "mi2" the last released version, and not the=20
> next version.  This gives better consistency between the last branch and=20
> the current release - "mi" should select the same thing - and that might=20
> encourage people to pick up current snaps.
> 
> I expect adding this to 6.0 and mainline in a few days.
> 
> I should note that I'm not sure how consistent my rollover process is -=20
> I suspect last time "mi" ended up selecting the mainline, instead of the=20
> previous released version.  I guess, given miN as the default, the=20
> process is:
> 
> Freeze an MI version (on the branch):
> - delete mi{N-1}
> - make "mi" select mi{N+1}
> - copy mi{N+1}-*.exp to mi-*.exp, s/-i=3Dmi{N+1}/-i=3Dmi/
> 
> Start a new MI version (on the mainline):
> - add mi{N+2}
> - copy mi{N+1)-*.exp to mi{N+2}-*.exp, s/-i=3Dmi{N+1}/-i=3Dmi{N+2}/
> 
> thoughts?

The docs part is okay with me.