[cfe-dev] [LLVMdev] LLVM 3.4 Branch Freeze

[Sylvestre Ledru]

On 13/12/2013 17:24, Tom Stellard wrote:
> On Fri, Dec 13, 2013 at 02:45:51PM +0100, Óscar Fuentes wrote:
>> Hal Finkel <hfinkel at anl.gov> writes:
>>
>> [snip]
>>
>>> Many of my colleagues say that, with gcc, they wait for
>>> the x.y.1 release before upgrading because the .0 is too buggy. But if
>>> we're not doing point releases, then I think we need tighter standards
>>> for release. Doing otherwise is not fair to our users.
>> What happened to the LLVM/Clang maintenance release project?
>>
> We weren't able to make a 3.3.1 release, because we did not have enough
> testers.
>
> In order to have a successful maintenance release, we need to either:
>
> a) Get commitments from everyone who wants a maintenance release that
> they will help test the release.
>
> or
>
> b) Have less strict testing requirements for maintenance releases with
>    the assumption that there is a lot of ongoing testing between .0 and .1
>    so there are less likely to be bugs left when it is time to release .1,
>    and anyone who cares about a maintenance release has had enough time to file
>    bugs.
>
> I really think maintenance releases are really important for Open Source
> projects, because these projects get much more testing after a release than
> before it.
>
>From the packager perspective, I totally agree with you.
I have set up some jenkins nodes to produce nightly packages for Debian
and Ubuntu for the 3.4 branches.
(I have some gcc-4.8 missing dependencies issues but they are not
directly related).

Sylvestre