[development] no 4-7-0 branch for core yet?

[Chris Johnson]

If people who are running the latest beta on their sites are not reporting 
show-stopping problems (and it does not seem that they are), then it should be 
a release candidate.

I agree with Khalid:  it ought to be called 5.0.  It might not be 
psychologically wise to change names at this point, but if release numbers are 
to make any sense, any changes the size of what were made between 4.6 and 4.7 
should really be major release number changes, e.g 4.6 -> 5.0, not point releases.

..chris

Khalid B wrote:
> +1 release candidate.
> 
> (Crazy idea: should 4.7 be renamed 5.0?  I wonder why Drupal went so
> fast from 1.0 -> 4.x, then languished 4.x land for some long, years for
> 4.2, 4.3, 4.4, 4.5, 4.6 too long)
> 
> The changes are huge under the hood, and porting modules to forms API
> is non trivial.
> 
> Would it be better to call it 5.0?
> 
> (Ducks under the desk).
> 
> On 2/20/06, Moshe Weitzman <weitzman at tejasa.com> wrote:
>> Dries Buytaert wrote:
>>> The tag (branch) doesn't exist yet.  Creating the branch complicates
>>> matters as we have to commit each patch twice.  I wanted to create  the
>>> branch as soon we release a 'release candidate'.  Talking of  which,
>>> should we release another beta (beta 5) or should we go  straight to a
>>> release candidate?
>> release candidate
>>
> 
>