Hello
I am a happy user of the Trinity 3.5.12. With the approaching date of release of 3.5.13, I rejoiced - at the earliest. However, already in the days before the release was seen reporting a number of problems and regressions. I was embarrassed. I would like to use 3.5.13, but some of the problems are fundamental. But even waiting for the R14 is not a good solution.
I would like to help so that I backport patches for repair of critical problems in 3.5.13. I have a patched version of kdelibs (closing 569), kdebase (closing 690) and kmymoney (closing 672) compiled into packages for Debian Squeeeze (sources, amd64 and i386). I would like to provide packages to the official repository.
Further I still watch KMail related errors (especially 635) and Kaffeine crashes (eg 559). And if you would be interested in this job, I might backport some other patches.
Best regards, Slavek --
Hello
I am a happy user of the Trinity 3.5.12. With the approaching date of release of 3.5.13, I rejoiced - at the earliest. However, already in the days before the release was seen reporting a number of problems and regressions. I was embarrassed. I would like to use 3.5.13, but some of the problems are fundamental. But even waiting for the R14 is not a good solution.
I would like to help so that I backport patches for repair of critical problems in 3.5.13. I have a patched version of kdelibs (closing 569), kdebase (closing 690) and kmymoney (closing 672) compiled into packages for Debian Squeeeze (sources, amd64 and i386). I would like to provide packages to the official repository.
Further I still watch KMail related errors (especially 635) and Kaffeine crashes (eg 559). And if you would be interested in this job, I might backport some other patches.
Best regards, Slavek
Hi Slavek,
If you are interested in helping to backport patches to the stable repositories for Debian and Ubuntu I would welcome the assistance.
When applying a patch to the official packages, the patched package needs to be updated for Debian and Ubuntu, across all the distro versions (Lucid, Maverick, Natty, Oneiric, Squeeze) supported by v3.5.13 at the same time. You will need to be somewhat familiar with Launchpad, as we use the exact same system to process source uploads and build packages.
You would start by uploading your patched packages into a new 3.5.13-updates PPA. There they can receive testing from our userbase before being merged into the official repositories.
If this sounds like something you would like to do, please let me know and I will contact you off-list with account information.
Thank you for your offer!
Tim
Timothy Pearson wrote:
You would start by uploading your patched packages into a new 3.5.13-updates PPA. There they can receive testing from our userbase before being merged into the official repositories.
If this sounds like something you would like to do, please let me know and I will contact you off-list with account information.
I'm not sure how Git works, but wouldn't it be better to have something like a separate testing branch based on the 3.5.13 code (maybe also call it R13?) which could result in a new release like 3.5.13a or R13.1 instead of patching things with the package scripts?
Then packages based on this branch could be tested and maybe there could be a quicker bugfix release before R14 is released. At least all packagers could choose to get the source from this branch then and get a few more fixes already. Now it would be more effort for all the packagers to manually add fixes to their packaging scripts (which would only be temporarily as well).
Isn't it also easier for the infrastructure to have extra PPAs based on separate Git branches? In any case, regular updates to stable Trinity versions with only smaller bugfixes sounds like an attractive idea to me :)
Best regards, Julius
-
Julius Schwartzenberg -
Slávek Banko -
Timothy Pearson