un-obsoleting the m32r port for 6.0

un-obsoleting the m32r port for 6.0

[Doug Evans]

Andrew writes:
 > To translate: New GDB 6 schedule:
 > 
 > 2003-06-14: Branch warning (was today)
 > 2003-06-21: Branch (was 2003-06-14)
 > 2003-08-02: Release (was 2003-06-26)

Suppose the fsf gets the remaining bits of my assignment June 20th
and I submit a patch to unobsolete the m32r June 22.
Can it still go into 6.0?

[If Renesas beats me to it, excellent.]

No claim is made that these dates are accurate of course.
I just want to get a feeling for how much time I have.

Re: un-obsoleting the m32r port for 6.0

[Andrew Cagney]

> Andrew writes:
>  > To translate: New GDB 6 schedule:
>  > 
>  > 2003-06-14: Branch warning (was today)
>  > 2003-06-21: Branch (was 2003-06-14)
>  > 2003-08-02: Release (was 2003-06-26)

There is also a respin, which after adjustment is Sept 27.

> Suppose the fsf gets the remaining bits of my assignment June 20th
> and I submit a patch to unobsolete the m32r June 22.

This is the branch commit policy:
http://sources.redhat.com/gdb/current/onlinedocs/gdbint_15.html#SEC132

In the past, GDB has allowed the addition of a new architecture to a 
release branch - s390 and ARV for instance.  The exact timing varies, 
for instance being added to the respin.

> [If Renesas beats me to it, excellent.]

Kei Sakamoto has tabled a patch.

> No claim is made that these dates are accurate of course.
> I just want to get a feeling for how much time I have.

I'd be more focused on the respin date.

Andrew