uClibc-0.9.30.3-rc1

[Ed W]

On 03/03/2010 18:01, Bernhard Reutner-Fischer wrote:
> During the weekend I've been pondering to release master as 0.9.31 now
> (without NPTL), branch it so we can cleanup master after the NPTL merge.
> In my mind this would be the best approach:
>
> .plan is now:
> tag 0.9.30.3 off the 0_9_30 branch, push a tarball.
> declare master frozen, push a 0.9.31-rc1 tarball (resp point people to
> e.g.
> http://git.uclibc.org/uClibc/snapshot/uClibc-63859f89f327e48037a4cdba982cd6afa3007da7.tar.bz2
> to be called 0.9.31-rc1; That's current master ATM).
> wait and fixup; branch 0.9.31, release it.
> merge NPTL into master (later on to be known as 0.9.32).
>
>    

Why not more visibly fork and maintain both 0.9.31 and 0.9.32 branches 
in parallel (at least to a certain degree)?

It might attract more testing and development if the nptl branch was 
technically "released", albeit with some caveats.  0.9.31 could be 
maintained for some period until the nptl releases are stable enough?

Just a thought...

Ed W