|
From: Christian B. <bor...@de...> - 2010-09-27 12:10:31
|
Am 27.09.2010 11:18, schrieb Julian Seward:
>
> Greetings.
>
> It's time to do a new release -- in fact, it's well overdue.
>
> I'm proposing to make a release in 3 weeks, on Monday 18 October.
Cool.
> In previous releases it's been inconvenient to have to freeze the
> trunk as release day draws near, so I am proposing this time to
> make the 3.6 branch one week before that (11 Oct) and
> stabilise/release from the branch. That means a bit more work
> moving changes between branches, but I think it's worth it.
I think it makes a lot of sense.
>
> The release platforms will be: {x86,amd64,arm,ppc32,ppc64}-linux
> and {x86,amd64}-darwin.
Given that valgrind become more and more a cross-platform tool,
I would like to ask for more review of the s390x port.
The s390x port has matured significantly - see
https://bugs.kde.org/show_bug.cgi?id=243404.
I understand that this change is too big for 3.6, but I would like
to target the following release for s390x integration.
We planned to do an updated patch against 3.6. I guess this means we
need two patches then, one against 3.6 and one against trunk after
the 3.6 release. As an alternative we could send un updated patch
on 11 Oct that matches both.
I would also like to have some feedback and code review from interested
parties and tool maintainers (e.g. what else needs to be done for
integration) and therefore updated the patches to r11383/r2046.
In addition, can architecture maintainers check that these patches dont
break anything for them. (arm, ppc, x86, amd64, darwin ...)?
Thanks
Christian
|