<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
FWIW, for our ARM Compiler product, we follow top-of-trunk, not the releases.
<div class="">Next to picking up new functionality quicker, it also allows us to detect regressions</div>
<div class="">in LLVM against our in-house testing quickly, not 6 months later. We find that when</div>
<div class="">we find a regression within 24 to 48 hours of the commit introducing it, it's much</div>
<div class="">cheaper to get it fixed.</div>
<div class=""><br class="">
</div>
<div class="">In my opinion, it would be better overall for the LLVM project if top-of-trunk is</div>
<div class="">tested as much as possible, if testing resources are so scarce that a choice</div>
<div class="">has to be made between testing top-of-trunk or testing a release branch.</div>
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class=""><br class="">
</div>
<div class="">Kristof</div>
<div class=""><br class="">
</div>
<div>
<blockquote type="cite" class="">
<div class="">On 12 May 2016, at 02:10, Robinson, Paul <<a href="mailto:paul.robinson@sony.com" class="">paul.robinson@sony.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="" class="">
<blockquote type="cite" style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
-----Original Message-----<br class="">
From: Renato Golin [<a href="mailto:renato.golin@linaro.org" class="">mailto:renato.golin@linaro.org</a>]<br class="">
Sent: Wednesday, May 11, 2016 11:11 AM<br class="">
To: Hans Wennborg<br class="">
Cc: LLVM Dev; Clang Dev; Quentin Colombet; Tom Stellard; Robinson, Paul;<br class="">
Jim Grosbach; Kristof Beyls; Frédéric Richez; Reid Kleckner; Philip<br class="">
Reames; Matthias Braun; Bernhard Rosenkränzer; Sylvestre Ledru; Matthias<br class="">
Klose; Stephen Hines; Jeff Law; Ed Maste; Behan Webster<br class="">
Subject: Re: LLVM Releases: Upstream vs. Downstream / Distros<br class="">
<br class="">
On 11 May 2016 at 17:16, Hans Wennborg <<a href="mailto:hans@chromium.org" class="">hans@chromium.org</a>> wrote:<br class="">
<blockquote type="cite" class="">This is a long email :-) I've made some comments inline, but I'll<br class="">
summarize my thoughts here:<br class="">
</blockquote>
<br class="">
Thanks Hans!<br class="">
<br class="">
I'll respond them inline, below.<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">- I think we should use the bug tracker to capture issues that affect<br class="">
releases. It would be cool if a commit hook could update bugzilla<br class="">
entries that refer to it.<br class="">
</blockquote>
<br class="">
That seems like a simple hook.<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">At least for the major releases, I think we're doing pretty well on<br class="">
timing in terms of predictability: since 3.6, we have release every<br class="">
six months: first week of March and first week of September (+- a few<br class="">
days). Branching has been similarly predictive: mid-January and<br class="">
mid-July.<br class="">
</blockquote>
<br class="">
Indeed, we got a lot better more recently (last 2y), and mostly thanks<br class="">
to you. :)<br class="">
</blockquote>
<br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Absolutely.
It's enough of a track record to allow reasonable planning.</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<blockquote type="cite" style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br class="">
We used to vary 3 months +-, and now we're down to a few days.<br class="">
Whatever we decide, I think we should make it official but putting it<br class="">
out somewhere, so people can rely on that.<br class="">
</blockquote>
<br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">A
public commitment to the future release schedule would be that much</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">more
justification for planning to participate.</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<blockquote type="cite" style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br class="">
Right now, even if you're extra awesome, there's nothing telling the<br class="">
distros and LLVM-based products that it will be so if someone else<br class="">
takes over the responsibility, so they can't adapt.<br class="">
<br class="">
That's what I meant by "quasi-chaotic".<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">If there are many downstream releases for which shifting this schedule<br class="">
would be useful, I suppose we could do that, but it seems unlikely<br class="">
that there would be agreement on this, and changing the schedule is<br class="">
disruptive for those who depend on it.<br class="">
</blockquote>
<br class="">
That's the catch. If we want them to participate, the process has to<br class="">
have some meaning to them. The fact that not many people do, is clear<br class="">
to me what it means.<br class="">
<br class="">
We also need to know better how many other releases already depend on<br class="">
the upstream process (not just Chromium, for obvious reasons), to be<br class="">
able to do an informed choice of dates and frequency.<br class="">
<br class="">
The more well positioned and frequent we are, the more people will<br class="">
help, but there's a point where the curve bends down, and the cost is<br class="">
just too great. We need to find the inflection point, and that will<br class="">
require some initial investigations and guesses, and a lot of fine<br class="">
tuning later. But if we're all on the same page, I think we can do<br class="">
that, even if it takes time.<br class="">
<br class="">
I'm particularly concerned with Android, because they not only have<br class="">
their own tree with heavily modified LLVM components (ex.<br class="">
Compiler-RT), but they also build differently and so their process are<br class="">
completely alien to ours. One of the key reasons why these things<br class="">
happened is because:<br class="">
<br class="">
* They couldn't rely on our releases, as fixing bugs and back-porting<br class="">
wasn't a thing back then<br class="">
* They already had their own release schedule, so aligning with ours<br class="">
brought no extra benefit<br class="">
* We always expected people to work off trunk, and everyone had to<br class="">
create their own process<br class="">
<br class="">
I don't want to change how people work, just to add one more valid way<br class="">
of working, which is most stable for upstream releases. :)<br class="">
<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">The only reasonable way I see of aligning upstream releases with<br class="">
downstream schedules would be to release much more often. This works<br class="">
well in Chromium where there's a 6-week staged release schedule. This<br class="">
would mean there's always a branch going for the next release, and<br class="">
important bug fixes would get merged to that.<br class="">
</blockquote>
<br class="">
Full validation every 6 weeks is just not possible. But a multiple of<br class="">
that, say every 3~4 months, could be much easier to work around.<br class="">
<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">In Chromium we drive<br class="">
this from the bug tracker -- it would be very hard to scan each commit<br class="">
for things to cherry-pick. This kind of process has a high cost<br class="">
though, there has to be good infrastructure for it (buildbots on the<br class="">
branch for all targets, for example), developers have to be aware, and<br class="">
even then it's a lot of work for those doing the releases. I'm not<br class="">
sure we'd want to take this on. I'm also not sure it would be suitable<br class="">
for a compiler, where we want the releases to have long life-time.<br class="">
</blockquote>
<br class="">
This works because you have a closed system. As you say, Chromium is<br class="">
mostly final product, not a tool to develop other products, and the<br class="">
validation is a lot simpler.<br class="">
<br class="">
With Clang, we'd want to involve external releases into it, and it<br class="">
simply wouldn't scale.<br class="">
<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">For the major releases, I've tried to do this. We could certainly<br class="">
formalize it by posting it on the web page though.<br class="">
</blockquote>
<br class="">
I think that'd be the first step, yes. But I wanted to start with a<br class="">
good number. 2 times a year? Would 3 times improve things that much<br class="">
for the outsiders? Or just moving the dates would be enough for most<br class="">
people?<br class="">
<br class="">
That's why I copied so many outsiders, so they can chime in and let us<br class="">
know what would be good for *them*.<br class="">
</blockquote>
<br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Data
point: At Sony we ship our stuff every 6 months and that isn't</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">going
to change. Our policy has been to base our releases on upstream</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">releases,
and given our current lead times, the current upstream release</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">schedule
is actually not bad, especially if it has stopped drifting.</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Having
four releases pretty consistently follow the current schedule is</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">extremely
positive, thanks!</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">It
would help our internal planning to publish the schedule for future</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">releases.
You never know, we might even be able to fork an internal</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">branch
in time to help with the release testing, although that is not</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">in
any way a lightweight process (so no promises).</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">There
has been some talk about moving toward releasing from upstream</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">trunk,
or more precisely to streamlining our internal testing process</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">in
order to allow us to seriously contemplate releasing from upstream</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">trunk.
I can't argue with the streamlining part, for sure. Whether</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">the
rest of it works out must remain to be seen.</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">--paulr</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<blockquote type="cite" style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br class="">
<br class="">
<blockquote type="cite" class="">Most importantly, those folks should get involved :-)<br class="">
</blockquote>
<br class="">
Indeed!<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">In practice, we kind of have this for at least some of the targets.<br class="">
Maybe we should write this down somewhere instead of me asking for<br class="">
(the same) volunteers each time the release process starts?<br class="">
</blockquote>
<br class="">
I give consent to mark me as the ARM/AArch64 release tester for the<br class="">
foreseeable future. :)<br class="">
<br class="">
I can also help Sylvestre, Doko, Ed, Jeff, Bero etc. to test on their<br class="">
system running on ARM/AArch64 hardware.<br class="">
<br class="">
cheers,<br class="">
--renato</blockquote>
</div>
</div>
</blockquote>
</div>
<br class="">
</body>
</html>