REMINDER: Release 3.6.0-alpha1 from master

[Petr Mladek]

Hi Rainer,

first thanks for your valuable input.

Rainer Bielefeld píše v Út 29. 05. 2012 v 19:45 +0200:
> Petr Mladek schrieb:
> 
> >> we are one week from the feature freeze for 3.6 release. We are going
> >> to provide 3.6.0-alpha1 build from master this week. I would like to do
> >> the tag tomorrow.
> 
> Hi,
> 
> from WIN user's view I doubt that that alpha will be usable for 
> intensive tests:
> "Bug 48946 - not find JRE"
>   <https://bugs.freedesktop.org/show_bug.cgi?id=48946>
>   Even Help will be unusable, and my suspect is that there is some
>   disastrous relation to some other crash problems we see.

Ah, we need to fix this before beta1 build, definitely.

Note that alpha1 is there to find exactly this kind of problems. Of
course, it does not make sense to produce it if is would be completely
unusable. On the other hand, we do not want to push it on mirrors. We
will not widely announce it. It might help to find similar problems also
on Linux or MAC. Also it is just a test of buildability with the release
configuration.


>   I still see the problem with a MinGW build
>   pull time 2012-05-28 04:23:12
> "Bug 50344 - Basic Macro will not run because of missing Java
>   <https://bugs.freedesktop.org/show_bug.cgi?id=50344>

Ah, it is not that critical if it works with the normal Windows build.
Note that MinGW build is still experimental and it is not ready for
production use. It is great that you test it but MinGW-specific bugs
can't block the normal release.

> Additionally I still am not able to do intensive tests to find the 
> reason for the frequent crashes hindering me from using daily Master 
> builds for intensive tests.

Ah, this scares me. We need a reproducible scenario and backtrace. I am
afraid that we will not be able to locate this problem before releasing
beta1. On the other hand, beta1 testing might bring more testers and
more scenarios of the crashes. It might help to locate the problem.

> IMHO it's not useful to start an alpha before the Java detection problem 
> has been solved.

Thanks for pointing it out. It is indeed very important bug. We will try
to solve it but I am not sure if it is a blocker for alpha build.


Best Regards,
Petr