Doing a release?

Khem Raj raj.khem at gmail.com
Wed Sep 18 16:11:43 UTC 2013


On Sep 17, 2013, at 9:49 PM, Thomas Petazzoni <thomas.petazzoni at free-electrons.com> wrote:

> Dear uClibc developers,
> 
> The last release of uClibc, 0.9.33.2, has been made well over a year
> ago. However, there is fairly big number of improvements/fixes in the
> master branch that would be interesting to have in a release. At the
> Buildroot level, we now have 53 patches in your patch stack against
> uClibc 0.9.33.2, all coming from the master branch if I'm correct (see
> http://git.buildroot.net/buildroot/tree/package/uclibc/0.9.33.2).
> 
> It'd be really nice if uClibc adopted a slightly more frequent release
> schedule, to more easily allow downstream users to benefit from
> improvements/fixes.

I think, if we decide to do releases biannually maintaining branches for long time
can be avoided. To get started I think lets start by planning for a 0.9.34 and then
everyone sending the pending patches for subsequent 0.9.35 and so on.

> 
> Thanks a lot!
> 
> Thomas
> -- 
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
> _______________________________________________
> uClibc mailing list
> uClibc at uclibc.org
> http://lists.busybox.net/mailman/listinfo/uclibc



More information about the uClibc mailing list