29 Aug
2012
29 Aug
'12
4:01 p.m.
Dne st 29. srpna 2012 Darrell Anderson napsal(a):
The overall lack of inactivity affects our image.
The growing size of the bug tracker affects our image because
resolutions are not forthcoming in equal or higher numbers.
We're going to get the usal slew of comments one way or another. :-)
Darrell
It is true that from originally expected "small" update the work has grown
greatly. 3.5.13.1 now contains a large number of fixes. If we were
release updated versions more often, it could be now for example
3.5.13.5 :)
However, I would suggest to leave the version as it is now == 3.5.13.x and
R14.x.x. I believe that the changing version labels now would be for
others confusing rather than helpful. For me, from experiences gained by
working on the SRU, follows that for future bugfix versions instead of
focusing on solving "all" discovered bugs we should prefer to release
bugfix versions more often.
My tasklist for 3.5.13.1 contain:
+ fix kstreamripper - bugs #1189, #946
- now I have patch for v3.5.13-sru, but I want to put it to be in
accordance with changes in R14
+ fix kde-guidance - bug #1188
- it should be simple - but help is welcome
+ fix kde-style-qtcurve - bug #1109
- I need help with this
+ create v3.5.13-sru branch on meta-project 'tde'
- I have almost done - soon I will send a draft modifications to scripts
to be applicable for all GIT branches
+ cherry-pick patches to change doc path from kde/HTML to tde/HTML
- patches is a lot, but integration should be straightforward - this
should be done quickly
Slavek
--
Push that as a release asap!
I won't be able to run an official build set from anything
other than GIT head, but if Slavek has 3.5.13.1 built for all our
supported Debian and Ubuntu versions I can go ahead and release an
SRU from that.
Slavek or someone better acquainted with GIT than I am will
need to generate source tarballs as well, as I cannot use the normal
automation to generate tarballs from an SRU tag in GIT.
You know as well as I do that we're going to get the usual
slew of "they still use HAL", "network-manager doesn't work",
"where
are the new features", etc. from the community if 3.5.13.1 is
released as 3.5.14. This would further damage our image and I
strongly recommend against it. Releasing an SRU instead indicates
that we are concerned about product quality.