Hello,
I've now checked the Linaro branding changes in to the gdb-linaro Bazaar repository.
I've created a Wiki page describing the Linaro GDB release process based on that repository: http://wiki.linaro.org/WorkingGroups/ToolChain/GDBReleaseProcess
(modeled after Andrew's GCCReleaseProcess page)
Review and comments are welcome!
Mit freundlichen Gruessen / Best Regards
Ulrich Weigand
-- Dr. Ulrich Weigand | Phone: +49-7031/16-3727 STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E. IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht Stuttgart, HRB 243294
On 22 September 2010 18:36, Ulrich Weigand Ulrich.Weigand@de.ibm.com wrote:
I've created a Wiki page describing the Linaro GDB release process based on that repository: http://wiki.linaro.org/WorkingGroups/ToolChain/GDBReleaseProcess (modeled after Andrew's GCCReleaseProcess page)
I have in turn used this as a pattern for writing up my notes/Loic's instructions on how to package a valgrind snapshot, so thanks! https://wiki.linaro.org/WorkingGroups/ToolChain/ValgrindReleaseProcess (it still has a few TODO entries in it, though...)
-- PMM
Peter Maydell wrote:
On 22 September 2010 18:36, Ulrich Weigand Ulrich.Weigand@de.ibm.com wrote:
I've created a Wiki page describing the Linaro GDB release process based on that repository: http://wiki.linaro.org/WorkingGroups/ToolChain/GDBReleaseProcess (modeled after Andrew's GCCReleaseProcess page)
I have in turn used this as a pattern for writing up my notes/Loic's instructions on how to package a valgrind snapshot, so thanks! https://wiki.linaro.org/WorkingGroups/ToolChain/ValgrindReleaseProcess (it still has a few TODO entries in it, though...)
Peter, 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. 2. During our testing, if we find bugs or regressions, what shall we do?
-- PMM
linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
On 25 September 2010 14:28, Yao Qi yao.qi@linaro.org wrote:
Peter Maydell wrote:
https://wiki.linaro.org/WorkingGroups/ToolChain/ValgrindReleaseProcess (it still has a few TODO entries in it, though...)
The process is very clear. Some questions here,
- 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 Linaro-specific patches * 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 stable codebase * 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.
- 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.)
-- PMM
Peter Maydell wrote:
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.
Yeah, I agree.
- 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.)
-- PMM
On Fri, Sep 24, 2010, Peter Maydell wrote:
I have in turn used this as a pattern for writing up my notes/Loic's instructions on how to package a valgrind snapshot, so thanks! https://wiki.linaro.org/WorkingGroups/ToolChain/ValgrindReleaseProcess (it still has a few TODO entries in it, though...)
Good notes on the valgrind release process; close to what I used to do at least
On 27 September 2010 10:08, Loïc Minier loic.minier@linaro.org wrote:
Good notes on the valgrind release process; close to what I used to do at least
Yes, I should be thanking you as well, there's a reason you find them familiar :-)
-- PMM
linaro-toolchain@lists.linaro.org
-
Loïc Minier -
Peter Maydell -
Ulrich Weigand -
Yao Qi