Linaro GDB release process
peter.maydell at linaro.org
Sun Sep 26 18:02:59 BST 2010
On 25 September 2010 14:28, Yao Qi <yao.qi at linaro.org> wrote:
> Peter Maydell wrote:
>> (it still has a few TODO entries in it, though...)
> The process is very clear. Some questions here,
> 1. In each release cycle, when do we make a snapshot from upstreams? We
> should allocate some time for testing.
The situation with valgrind is a little bit different from what it
is with gcc, for instance:
* we're tracking valgrind upstream and applying few or no
* valgrind is a 'minor tool' and so bugs in it are less catastrophic
* ARM/Thumb support has just landed upstream so we expect
an initial period of flushing out bugs but subsequently a fairly
* at the moment there is no usable valgrind for ARM unless
you are pulling upstream svn, so any snapshot is an
improvement on the status quo
So we want to put our first snapshot out as soon as
possible, labelled as a 'developer preview' or 'beta', to encourage
people to start using it on ARM platforms and to report bugs.
We can then work with upstream to hopefully get these bugs
fixed by the time the valgrind 3.6.0 release occurs. After that
we will probably be able to drop the Linaro-specific package and
fold things back into Ubuntu. So my feeling is that this won't
necessarily be a regular "once per release cycle" sort of activity.
> 2. During our testing, if we find bugs or regressions, what shall we do?
As I've encountered bugs while doing pre-snapshot testing I've
been reporting them upstream to Julian who has fixed them
all very quickly. (The bugs are generally of the "instruction not
yet implemented" form.)
More information about the linaro-toolchain