Hey guys,
Thanks to the hard work of our excellent team members 3.5.13 SRU is almost ready to be released.
Slavek has mentioned a tentative release date of October 1st, which is a week away.
So we need:
1. A press release ready and have a list of people we want to send it to. That list has already been compiled. Here is a link to the press release etherpad. http://trinity.etherpad.trinitydesktop.org/55 2. Sync'd mirrors - Slavek, Tim, is there enough time to do this in 1 week or should we push release back further? 3. Updated website - Tim - what do I need to do to make this happen? 4. Updated wiki - We should make sure we aren't leaving any gaping holes here on the wiki about 3.5.13 SRU. http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13_1_...
Calvin
On Wednesday 26 of September 2012 01:39:31 Calvin Morrison wrote:
Hey guys,
Thanks to the hard work of our excellent team members 3.5.13 SRU is almost ready to be released.
Slavek has mentioned a tentative release date of October 1st, which is a week away.
So we need:
- A press release ready and have a list of people we want to send it
to. That list has already been compiled. Here is a link to the press release etherpad. http://trinity.etherpad.trinitydesktop.org/55 2. Sync'd mirrors - Slavek, Tim, is there enough time to do this in 1 week or should we push release back further? 3. Updated website - Tim - what do I need to do to make this happen? 4. Updated wiki - We should make sure we aren't leaving any gaping holes here on the wiki about 3.5.13 SRU. http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13_1 _Changelog
Calvin
François, please, can you supplement to the draft announcement of a new version your large list of distributions and versions for which you prepare packages?
Thanks Slávek --
On Wednesday 26 of September 2012 01:39:31 Calvin Morrison wrote:
- Sync'd mirrors - Slavek, Tim, is there enough time to do this in 1
week or should we push release back further?
While working on v3.5.13-sru I have achieved a significant reduction in size of the source packages for Debian and Ubuntu. First I noticed that in the Debian / Ubuntu source packages was contained metadata SVN - removing them the size decreased almost by 50%. Then I also replaced the gzip by bzip - the size was reduced by approximately 15%. The last step was the most significant that for SRU I changed package format from "native" to "quilt". This became the source file common to all versions of Debian and Ubuntu - the size was reduced by almost 80%. This allows the overall size of the source packages reduced to about 12% of its original size for 3.5.13.
Although the packages were added for new distribution (Precise), by reducing the size of the source packages, the total size of the PPA is lower than the original 3.5.13 - about 5 GiB.
Slavek --
On Wednesday 26 of September 2012 01:39:31 Calvin Morrison wrote:
- Sync'd mirrors - Slavek, Tim, is there enough time to do this in 1
week or should we push release back further?
While working on v3.5.13-sru I have achieved a significant reduction in size of the source packages for Debian and Ubuntu. First I noticed that in the Debian / Ubuntu source packages was contained metadata SVN - removing them the size decreased almost by 50%. Then I also replaced the gzip by bzip - the size was reduced by approximately 15%. The last step was the most significant that for SRU I changed package format from "native" to "quilt". This became the source file common to all versions of Debian and Ubuntu - the size was reduced by almost 80%. This allows the overall size of the source packages reduced to about 12% of its original size for 3.5.13.
Although the packages were added for new distribution (Precise), by reducing the size of the source packages, the total size of the PPA is lower than the original 3.5.13 - about 5 GiB.
Slavek
Interesting! Are you going to do this in the R14 packaging tree as well?
When you are ready to release please let me know, and I will copy your packages onto the mirror system via a new PPA.
Thanks!
Tim
On Friday 28 of September 2012 17:07:33 Timothy Pearson wrote:
When you are ready to release please let me know, and I will copy your packages onto the mirror system via a new PPA.
Thanks!
Supply of patches is stopped, the last compilation is already finished, so PPA seems to be ready for publishing.
I assumed that 3.5.13.1 will replace the existing packages in existing 3.5.13 PPA. In order to users do not need to setup a new apt source and just pulled them updates. You'll make new separate PPA for 3.5.13.1?
Slavek --
On Friday 28 of September 2012 17:45:16 Slávek Banko wrote:
On Friday 28 of September 2012 17:07:33 Timothy Pearson wrote:
When you are ready to release please let me know, and I will copy your packages onto the mirror system via a new PPA.
Thanks!
Supply of patches is stopped, the last compilation is already finished, so PPA seems to be ready for publishing.
I assumed that 3.5.13.1 will replace the existing packages in existing 3.5.13 PPA. In order to users do not need to setup a new apt source and just pulled them updates. You'll make new separate PPA for 3.5.13.1?
Slavek
Note: I have in my PPA also some packages that are in the build-deps. Updated libart, libcaldav and libcarddav. And then all the necessary build-deps for Precise.
Slavek --
On 28 September 2012 12:12, Slávek Banko slavek.banko@axis.cz wrote:
On Friday 28 of September 2012 17:45:16 Slávek Banko wrote:
On Friday 28 of September 2012 17:07:33 Timothy Pearson wrote:
When you are ready to release please let me know, and I will copy your packages onto the mirror system via a new PPA.
Thanks!
Supply of patches is stopped, the last compilation is already finished, so PPA seems to be ready for publishing.
I assumed that 3.5.13.1 will replace the existing packages in existing 3.5.13 PPA. In order to users do not need to setup a new apt source and just pulled them updates. You'll make new separate PPA for 3.5.13.1?
Slavek
Note: I have in my PPA also some packages that are in the build-deps. Updated libart, libcaldav and libcarddav. And then all the necessary build-deps for Precise.
Slavek
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Why not use XZ? it's even better than bzip2
Calvin
On Friday 28 of September 2012 18:18:00 Calvin Morrison wrote:
Why not use XZ? it's even better than bzip2
Calvin
I'm not sure if all supported versions of Debianu / Ubuntu have support for XZ in deb packages.
Slavek --
On 30 September 2012 20:13, Slávek Banko slavek.banko@axis.cz wrote:
On Friday 28 of September 2012 18:18:00 Calvin Morrison wrote:
Why not use XZ? it's even better than bzip2
Calvin
I'm not sure if all supported versions of Debianu / Ubuntu have support for XZ in deb packages.
Slavek
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
XZ is awesome - in the future you should use it for at least all supported packages. Archlinux switched a while back and it has been a blessing on my bandwidth
On Friday 28 of September 2012 17:45:16 Slávek Banko wrote:
On Friday 28 of September 2012 17:07:33 Timothy Pearson wrote:
When you are ready to release please let me know, and I will copy your packages onto the mirror system via a new PPA.
Thanks!
Supply of patches is stopped, the last compilation is already finished, so PPA seems to be ready for publishing.
I assumed that 3.5.13.1 will replace the existing packages in existing 3.5.13 PPA. In order to users do not need to setup a new apt source and just pulled them updates. You'll make new separate PPA for 3.5.13.1?
Slavek
Note: I have in my PPA also some packages that are in the build-deps. Updated libart, libcaldav and libcarddav. And then all the necessary build-deps for Precise.
Slavek
As the 3.5.13.1 packages are fully finalised I will just go ahead and overwrite the existing 3.5.13 packages in the release PPA. Before I do this though I would like to publish the 3.5.13.1 source tarballs to the mirror system; they are downloading from your server as I write this.
Thanks!
Tim
On Friday 28 of September 2012 18:26:02 Timothy Pearson wrote:
As the 3.5.13.1 packages are fully finalised I will just go ahead and overwrite the existing 3.5.13 packages in the release PPA. Before I do this though I would like to publish the 3.5.13.1 source tarballs to the mirror system; they are downloading from your server as I write this.
Thanks!
Tim
It's probably the most appropriate time for me to push to GIT commit to tdelibs to set version string to 3.5.13.1 (in tarballs and binary packages in my PPA is already included) and create tag for 3.5.13.1 on all git modules.
Slavek --
On Friday 28 of September 2012 18:26:02 Timothy Pearson wrote:
As the 3.5.13.1 packages are fully finalised I will just go ahead and overwrite the existing 3.5.13 packages in the release PPA. Before I do this though I would like to publish the 3.5.13.1 source tarballs to the mirror system; they are downloading from your server as I write this.
Thanks!
Tim
It's probably the most appropriate time for me to push to GIT commit to tdelibs to set version string to 3.5.13.1 (in tarballs and binary packages in my PPA is already included) and create tag for 3.5.13.1 on all git modules.
Slavek
Yes. I now have all your source tarballs and they are being published to the mirrors.
Do we have a release announcement ready to go yet?
Thanks!
Tim
On 28 September 2012 12:51, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
On Friday 28 of September 2012 18:26:02 Timothy Pearson wrote:
As the 3.5.13.1 packages are fully finalised I will just go ahead and overwrite the existing 3.5.13 packages in the release PPA. Before I do this though I would like to publish the 3.5.13.1 source tarballs to the mirror system; they are downloading from your server as I write this.
Thanks!
Tim
It's probably the most appropriate time for me to push to GIT commit to tdelibs to set version string to 3.5.13.1 (in tarballs and binary packages in my PPA is already included) and create tag for 3.5.13.1 on all git modules.
Slavek
Yes. I now have all your source tarballs and they are being published to the mirrors.
Do we have a release announcement ready to go yet?
Thanks!
Tim
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Darrell, Robert, Native English speakers abound,
Could you review the release annoucement?
On Friday 28 of September 2012 18:51:12 Timothy Pearson wrote:
On Friday 28 of September 2012 18:26:02 Timothy Pearson wrote:
As the 3.5.13.1 packages are fully finalised I will just go ahead and overwrite the existing 3.5.13 packages in the release PPA. Before I do this though I would like to publish the 3.5.13.1 source tarballs to the mirror system; they are downloading from your server as I write this.
Thanks!
Tim
It's probably the most appropriate time for me to push to GIT commit to tdelibs to set version string to 3.5.13.1 (in tarballs and binary packages in my PPA is already included) and create tag for 3.5.13.1 on all git modules.
Slavek
Yes. I now have all your source tarballs and they are being published to the mirrors.
Do we have a release announcement ready to go yet?
Thanks!
Tim
Please, can I create an annotated tag v3.5.13.1 with the comment: "Official Trinity Desktop Environment v3.5.13.1 release"?
Do you have an estimate of when they will be available to users both source and binary packages? Prepare someone "Release notes" for 3.5.13.1? Or will the modified release notes for 3.5.13?
Slavek --
On Friday 28 of September 2012 18:51:12 Timothy Pearson wrote:
On Friday 28 of September 2012 18:26:02 Timothy Pearson wrote:
As the 3.5.13.1 packages are fully finalised I will just go ahead and overwrite the existing 3.5.13 packages in the release PPA. Before I
do
this though I would like to publish the 3.5.13.1 source tarballs to
the
mirror system; they are downloading from your server as I write this.
Thanks!
Tim
It's probably the most appropriate time for me to push to GIT commit
to
tdelibs to set version string to 3.5.13.1 (in tarballs and binary packages in my PPA is already included) and create tag for 3.5.13.1 on all git modules.
Slavek
Yes. I now have all your source tarballs and they are being published to the mirrors.
Do we have a release announcement ready to go yet?
Thanks!
Tim
Please, can I create an annotated tag v3.5.13.1 with the comment: "Official Trinity Desktop Environment v3.5.13.1 release"?
Yes, go ahead.
Do you have an estimate of when they will be available to users both source and binary packages?
5Gb might take a couple of days to upload to all the mirrors.
Prepare someone "Release notes" for 3.5.13.1? Or will the modified release notes for 3.5.13?
This is important; we should not announce officially until this is done. Copying the 3.5.13 release notes and modifying the copy would be a good idea.
Tim
On Friday 28 of September 2012 20:02:55 Timothy Pearson wrote:
Do you have an estimate of when they will be available to users both source and binary packages?
5Gb might take a couple of days to upload to all the mirrors.
Note: 5 GiB is saving overall size compared with the previous 3.5.13 PPA. The total size for 3.5.13.1 is about 14 GiB.
Prepare someone "Release notes" for 3.5.13.1? Or will the modified release notes for 3.5.13?
This is important; we should not announce officially until this is done. Copying the 3.5.13 release notes and modifying the copy would be a good idea.
I wrote a bit of notes which could be used for release notes:
Packages that have been partially or completely broken and now are fixed: + kaffeine + kde-style-qtcurve + kgtk-qt3 + kio-locate + kmymoney + koffice + kstreamripper + ktorrent + kvirc
Interest fixes: + many fixes SAK + improvements locking screen + fixed kwin-style-keramik + performance improvements and fixes for IMAP in KMail + new version of package sudo-trinity (Debian, Ubuntu)
New packages: + gwenview-i18n + k3b-i18n + koffice-i18n
Slavek --
On Friday 28 of September 2012 20:02:55 Timothy Pearson wrote:
Do you have an estimate of when they will be available to users both source and binary packages?
5Gb might take a couple of days to upload to all the mirrors.
Note: 5 GiB is saving overall size compared with the previous 3.5.13 PPA. The total size for 3.5.13.1 is about 14 GiB.
Prepare someone "Release notes" for 3.5.13.1? Or will the modified release notes for 3.5.13?
This is important; we should not announce officially until this is done. Copying the 3.5.13 release notes and modifying the copy would be a good idea.
I wrote a bit of notes which could be used for release notes:
Packages that have been partially or completely broken and now are fixed:
- kaffeine
- kde-style-qtcurve
- kgtk-qt3
- kio-locate
- kmymoney
- koffice
- kstreamripper
- ktorrent
- kvirc
Interest fixes:
- many fixes SAK
- improvements locking screen
- fixed kwin-style-keramik
- performance improvements and fixes for IMAP in KMail
- new version of package sudo-trinity (Debian, Ubuntu)
New packages:
- gwenview-i18n
- k3b-i18n
- koffice-i18n
Slavek
Calvin, Darrell,
Do you have time to quickly throw together a release notes page for 3.5.13.1 on the Wiki, based on the release notes from 3.5.13? I made a copy for editing here: http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13_1
I would like to push out the 3.5.13.1 release ASAP, but unfortunately don't have much time this weekend to devote to the project, so any and all assistance is greatly appreciated!
Thanks!
Tim
On 29 September 2012 16:06, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
On Friday 28 of September 2012 20:02:55 Timothy Pearson wrote:
Do you have an estimate of when they will be available to users both source and binary packages?
5Gb might take a couple of days to upload to all the mirrors.
Note: 5 GiB is saving overall size compared with the previous 3.5.13 PPA. The total size for 3.5.13.1 is about 14 GiB.
Prepare someone "Release notes" for 3.5.13.1? Or will the modified release notes for 3.5.13?
This is important; we should not announce officially until this is done. Copying the 3.5.13 release notes and modifying the copy would be a good idea.
I wrote a bit of notes which could be used for release notes:
Packages that have been partially or completely broken and now are fixed:
- kaffeine
- kde-style-qtcurve
- kgtk-qt3
- kio-locate
- kmymoney
- koffice
- kstreamripper
- ktorrent
- kvirc
Interest fixes:
- many fixes SAK
- improvements locking screen
- fixed kwin-style-keramik
- performance improvements and fixes for IMAP in KMail
- new version of package sudo-trinity (Debian, Ubuntu)
New packages:
- gwenview-i18n
- k3b-i18n
- koffice-i18n
Slavek
Calvin, Darrell,
Do you have time to quickly throw together a release notes page for 3.5.13.1 on the Wiki, based on the release notes from 3.5.13? I made a copy for editing here: http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13_1
I would like to push out the 3.5.13.1 release ASAP, but unfortunately don't have much time this weekend to devote to the project, so any and all assistance is greatly appreciated!
Thanks!
Tim
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
I have a concert to attend to but I'll see what I can get done in the next 15.
Do we we need new screenshots or none at all? It seems preposterous to keep using the same one.
Calvin
<snip>
Do we we need new screenshots or none at all? It seems preposterous to keep using the same one.
Calvin
Did anything user-visible change in 3.5.13.1 vs. 3.5.13? I usually only update the screenshots when something visible has changed due to the need to install a stock TDE system first.
Tim
On Saturday 29 of September 2012 22:30:30 Timothy Pearson wrote:
<snip>
Do we we need new screenshots or none at all? It seems preposterous to keep using the same one.
Calvin
Did anything user-visible change in 3.5.13.1 vs. 3.5.13? I usually only update the screenshots when something visible has changed due to the need to install a stock TDE system first.
Tim
Looking at the current images - the second image - from the default page has been removed links About Kubuntu and Kubuntu Documentation. Instead of them was returned link to Settings.
Slavek --
On Saturday 29 of September 2012 22:30:30 Timothy Pearson wrote:
<snip>
Do we we need new screenshots or none at all? It seems preposterous to keep using the same one.
Calvin
Did anything user-visible change in 3.5.13.1 vs. 3.5.13? I usually only update the screenshots when something visible has changed due to the need to install a stock TDE system first.
Tim
Note: The press release can be modified to point to the new release notes, instead of the original 3.5.13 release notes.
Slavek --
I wrote a bit of notes which could be used for release notes:
Packages that have been partially or completely broken and now are fixed:
- kaffeine
- kde-style-qtcurve
- kgtk-qt3
- kio-locate
- kmymoney
- koffice
- kstreamripper
- ktorrent
- kvirc
Interest fixes:
- many fixes SAK
- improvements locking screen
- fixed kwin-style-keramik
- performance improvements and fixes for IMAP in KMail
- new version of package sudo-trinity (Debian, Ubuntu)
New packages:
- gwenview-i18n
- k3b-i18n
- koffice-i18n
Do you have time to quickly throw together a release notes page for 3.5.13.1 on the Wiki, based on the release notes from 3.5.13? I made a copy for editing here: http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13_1
I would like to push out the 3.5.13.1 release ASAP, but unfortunately don't have much time this weekend to devote to the project, so any and all assistance is greatly appreciated!
I suggest keeping the 3.5.13.1 page short because most of the work was bug fix and stability issues. That is, don't repeat the entire 3.5.13 page. Instead provide a link to the 3.5.13 page.
For the bug fix subsection, just provide a link to the wiki page:
http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13_1_...
Slavek,
Do you have notes regarding which commits are feature additions and improvements back ported from GIT rather than bug fixes? For example, the new i18n packages are not bug fixes. If we create a bullet list of several items then that would suffice.
Darrell
On Saturday 29 of September 2012 23:11:09 Darrell Anderson wrote:
I wrote a bit of notes which could be used for release notes:
Packages that have been partially or completely broken and now are fixed: + kaffeine
- kde-style-qtcurve
- kgtk-qt3
- kio-locate
- kmymoney
- koffice
- kstreamripper
- ktorrent
- kvirc
Interest fixes:
- many fixes SAK
- improvements locking screen
- fixed kwin-style-keramik
- performance improvements and fixes for IMAP in KMail
- new version of package sudo-trinity (Debian, Ubuntu)
New packages:
- gwenview-i18n
- k3b-i18n
- koffice-i18n
Do you have time to quickly throw together a release notes page for 3.5.13.1 on the Wiki, based on the release notes from 3.5.13? I made a copy for editing here: http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13 _1
I would like to push out the 3.5.13.1 release ASAP, but unfortunately don't have much time this weekend to devote to the project, so any and all assistance is greatly appreciated!
I suggest keeping the 3.5.13.1 page short because most of the work was bug fix and stability issues. That is, don't repeat the entire 3.5.13 page. Instead provide a link to the 3.5.13 page.
For the bug fix subsection, just provide a link to the wiki page:
http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13_1 _Changelog
Slavek,
Do you have notes regarding which commits are feature additions and improvements back ported from GIT rather than bug fixes? For example, the new i18n packages are not bug fixes. If we create a bullet list of several items then that would suffice.
Darrell
Again, I fished in the changelog, to pull list of improvements: + Screen locking (many improvements) + Placement of icons connected devices + Reorganizing KDE menu + Added KControl (Peripherals / Storage Media / Advanced) controls to set default mount options. + Utf8 encoding for webdav directories + Updated kate synatax highlighting files + Better kmix autostart + Default global shortcuts for kmix + Better Kaffeine support in Kopete now listening plugin + Performance improvements for IMAP + Ark support for Arj + Ark support for check archives + Utf8 enconding in filenames in Ark + Large files support in kio-locate + Changed screen saver control in KMPlayer + New keyboard shortcuts in KMPlayer + KMyMoney updated to 1.0.5 + KTorrent updated to 2.2.8 + New packages with localizations - gwenview-i18n, k3b-i18n, koffice-i18n
Slavek --
All,
I updated the 3.5.13.1 wiki page:
http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13_1
Feel free to edit further.
Darrell
All,
I updated the 3.5.13.1 wiki page:
http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13_1
Feel free to edit further.
Darrell
Looks good overall, except for the outdated Konqueror screenshot and the known issues section. Slavek, are the kommander and kmymoney issues referenced in that section fixed in 3.5.13.1?
Thanks!
Tim
On Sunday 30 of September 2012 23:04:48 Timothy Pearson wrote:
All,
I updated the 3.5.13.1 wiki page:
http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13 _1
Feel free to edit further.
Darrell
Looks good overall, except for the outdated Konqueror screenshot and the known issues section. Slavek, are the kommander and kmymoney issues referenced in that section fixed in 3.5.13.1?
Thanks!
Tim
Yes, KMyMoney and Kommander was in 3.5.13.1 already fixed.
Slavek --
On Sunday 30 of September 2012 23:04:48 Timothy Pearson wrote:
Looks good overall, except for the outdated Konqueror screenshot and the known issues section. Slavek, are the kommander and kmymoney issues referenced in that section fixed in 3.5.13.1?
Thanks!
Tim
It is up to me to create a new screenshot? Note: I have here only Debian.
Slavek --
On Sunday 30 of September 2012 23:04:48 Timothy Pearson wrote:
Looks good overall, except for the outdated Konqueror screenshot and the known issues section. Slavek, are the kommander and kmymoney issues referenced in that section fixed in 3.5.13.1?
Thanks!
Tim
It is up to me to create a new screenshot? Note: I have here only Debian.
Slavek
If you have 3.5.13.1 installed that might be easiest. If not let me know and I will try to generate one soon.
Tim
Our 3.5.13.1 release preparations look to be nearly complete at this point, and I am about ready to publish the SRU packages publicly.
Before I do this, can everyone please run through the release notes and press release, looking for any factual errors, grammatical issues, or missing information?
Release notes: http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13_1_... Press release: http://trinity.etherpad.trinitydesktop.org/55
I also would like to extend my sincere thanks to Slavek Banko, who has worked tirelessly to backport changes from the GIT tree and resolve bugs in both the 3.5.13 release and in GIT HEAD. Without his assistance this SRU would not have been possible.
Tim
Our 3.5.13.1 release preparations look to be nearly complete at this point, and I am about ready to publish the SRU packages publicly.
Before I do this, can everyone please run through the release notes and press release, looking for any factual errors, grammatical issues, or missing information?
Release notes: http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13_1_... Press release: http://trinity.etherpad.trinitydesktop.org/55
I also would like to extend my sincere thanks to Slavek Banko, who has worked tirelessly to backport changes from the GIT tree and resolve bugs in both the 3.5.13 release and in GIT HEAD. Without his assistance this SRU would not have been possible.
Tim
My apologies, the first link should be: http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13_1
Tim
Dne po 1. října 2012 Timothy Pearson napsal(a):
Our 3.5.13.1 release preparations look to be nearly complete at this point, and I am about ready to publish the SRU packages publicly.
Before I do this, can everyone please run through the release notes and press release, looking for any factual errors, grammatical issues, or missing information?
Release notes: http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_ 13_1_Changelog Press release: http://trinity.etherpad.trinitydesktop.org/55
I also would like to extend my sincere thanks to Slavek Banko, who has worked tirelessly to backport changes from the GIT tree and resolve bugs in both the 3.5.13 release and in GIT HEAD. Without his assistance this SRU would not have been possible.
Tim
In a press release are referred only original release notes 3.5.13. We want refer only original 3.5.13 realease notes, only new release notes 3.5.13.1, or both?
Slavek --
On Mon, Oct 1, 2012 at 8:42 AM, Slávek Banko slavek.banko@axis.cz wrote:
In a press release are referred only original release notes 3.5.13. We want refer only original 3.5.13 realease notes, only new release notes 3.5.13.1, or both?
Slavek
Just changed the reference to 3.5.13.1.
On Mon, Oct 1, 2012 at 8:46 AM, Robert Xu robxu9@gmail.com wrote:
On Mon, Oct 1, 2012 at 8:42 AM, Slávek Banko slavek.banko@axis.cz wrote:
In a press release are referred only original release notes 3.5.13. We want refer only original 3.5.13 realease notes, only new release notes 3.5.13.1, or both?
Slavek
Just changed the reference to 3.5.13.1.
I also decided to push Improvements up in the release notes because most people will probably want to refer to that.
Dne po 1. října 2012 Robert Xu napsal(a):
On Mon, Oct 1, 2012 at 8:46 AM, Robert Xu robxu9@gmail.com wrote:
On Mon, Oct 1, 2012 at 8:42 AM, Slávek Banko slavek.banko@axis.cz
wrote:
In a press release are referred only original release notes 3.5.13. We want refer only original 3.5.13 realease notes, only new release notes 3.5.13.1, or both?
Slavek
Just changed the reference to 3.5.13.1.
I also decided to push Improvements up in the release notes because most people will probably want to refer to that.
From my point of view, it looks all good. Press release, as well as the release notes. Thank you all.
Slavek --
Dne po 1. ÅÃjna 2012 Robert Xu napsal(a):
On Mon, Oct 1, 2012 at 8:46 AM, Robert Xu robxu9@gmail.com wrote:
On Mon, Oct 1, 2012 at 8:42 AM, Slávek Banko slavek.banko@axis.cz
wrote:
In a press release are referred only original release notes 3.5.13. We want refer only original 3.5.13 realease notes, only new release notes 3.5.13.1, or both?
Slavek
Just changed the reference to 3.5.13.1.
I also decided to push Improvements up in the release notes because most people will probably want to refer to that.
From my point of view, it looks all good. Press release, as well as the release notes. Thank you all.
Slavek
Packages have been copied from your PPA and are now being published to the mirror system. I therefore expect to officially announce 3.5.13.1 by 10/03/2012.
Tim
On Monday 01 of October 2012 23:41:19 Timothy Pearson wrote:
Packages have been copied from your PPA and are now being published to the mirror system. I therefore expect to officially announce 3.5.13.1 by 10/03/2012.
Tim
I just looked at one of the mirrors and I see there already some packages for Precise. I noticed that in the build-deps are not included akode, fireflies, libept-trinity and pcsc-lite-nodbus for Precise.
Slavek --
On Monday 01 of October 2012 23:41:19 Timothy Pearson wrote:
Packages have been copied from your PPA and are now being published to the mirror system. I therefore expect to officially announce 3.5.13.1 by 10/03/2012.
Tim
I just looked at one of the mirrors and I see there already some packages for Precise. I noticed that in the build-deps are not included akode, fireflies, libept-trinity and pcsc-lite-nodbus for Precise.
Slavek
The missing build-deps packages should now be in place; apparently the initial copy failed.
Tim
On Tuesday 02 of October 2012 03:10:05 Timothy Pearson wrote:
The missing build-deps packages should now be in place; apparently the initial copy failed.
Now I realized: Should I upload trinity-keyring package for precise? So far I did not have this package, as it was not an official source for Precise valid.
Slavek --
On Tuesday 02 of October 2012 03:10:05 Timothy Pearson wrote:
The missing build-deps packages should now be in place; apparently the initial copy failed.
Now I realized: Should I upload trinity-keyring package for precise? So far I did not have this package, as it was not an official source for Precise valid.
Slavek
Don't bother, I just uploaded it.
Tim
Dne út 2. října 2012 Timothy Pearson napsal(a):
On Tuesday 02 of October 2012 03:10:05 Timothy Pearson wrote:
The missing build-deps packages should now be in place; apparently the initial copy failed.
Now I realized: Should I upload trinity-keyring package for precise? So far I did not have this package, as it was not an official source for Precise valid.
Slavek
Don't bother, I just uploaded it.
Tim
Thank you. While viewing packages, I noticed that could be copied for Precise packages that I have no interest during preparation updates:
+ kde-xp + redmond-settings + redmond-settings-ii
Conversely package filelight-l10n can be safely removed for all distributions, because all its contents is in conflict with the package filelight, for which it was intended.
Thanks Slavek --
Dne út 2. ÅÃjna 2012 Timothy Pearson napsal(a):
On Tuesday 02 of October 2012 03:10:05 Timothy Pearson wrote:
The missing build-deps packages should now be in place; apparently the initial copy failed.
Now I realized: Should I upload trinity-keyring package for precise? So far I did not have this package, as it was not an official source for Precise valid.
Slavek
Don't bother, I just uploaded it.
Tim
Thank you. While viewing packages, I noticed that could be copied for Precise packages that I have no interest during preparation updates:
- kde-xp
- redmond-settings
- redmond-settings-ii
Conversely package filelight-l10n can be safely removed for all distributions, because all its contents is in conflict with the package filelight, for which it was intended.
Thanks Slavek --
Done!
Tim
On Friday 28 of September 2012 17:07:33 Timothy Pearson wrote:
Interesting! Are you going to do this in the R14 packaging tree as well?
I assume that the change native => quilt could be used for the final R14 and certainly for subsequent SRU in R14. In order to use quilt also for the nightly-builds, it requires to modify scripts that you use to prepare packages for nigtly-builds.
For example, it should need to change the version number used for base tarball "orig.tar.bz2" because it is not possible to use dash for a version of "upstream" package on Debian. Instead of 14.0.0-0debian11+r274+pr2~wheezy would have to be used, for example 14.0.0~r274 for the base tarball orig.tar.bz2. And distribution specific version would in this case be: 14.0.0~r274-0debian11~wheezy.
It is therefore a question, whether is now a good time for such a change?
Slavek --
On Friday 28 of September 2012 17:07:33 Timothy Pearson wrote:
Interesting! Are you going to do this in the R14 packaging tree as well?
I assume that the change native => quilt could be used for the final R14 and certainly for subsequent SRU in R14. In order to use quilt also for the nightly-builds, it requires to modify scripts that you use to prepare packages for nigtly-builds.
For example, it should need to change the version number used for base tarball "orig.tar.bz2" because it is not possible to use dash for a version of "upstream" package on Debian. Instead of 14.0.0-0debian11+r274+pr2~wheezy would have to be used, for example 14.0.0~r274 for the base tarball orig.tar.bz2. And distribution specific version would in this case be: 14.0.0~r274-0debian11~wheezy.
It is therefore a question, whether is now a good time for such a change?
Slavek
As this would require a change of the versioning scheme, now is not a good time for the change.
Tim
On Saturday 29 of September 2012 04:05:43 Timothy Pearson wrote:
On Friday 28 of September 2012 17:07:33 Timothy Pearson wrote:
Interesting! Are you going to do this in the R14 packaging tree as well?
I assume that the change native => quilt could be used for the final R14 and certainly for subsequent SRU in R14. In order to use quilt also for the nightly-builds, it requires to modify scripts that you use to prepare packages for nigtly-builds.
For example, it should need to change the version number used for base tarball "orig.tar.bz2" because it is not possible to use dash for a version of "upstream" package on Debian. Instead of 14.0.0-0debian11+r274+pr2~wheezy would have to be used, for example 14.0.0~r274 for the base tarball orig.tar.bz2. And distribution specific version would in this case be: 14.0.0~r274-0debian11~wheezy.
It is therefore a question, whether is now a good time for such a change?
Slavek
As this would require a change of the versioning scheme, now is not a good time for the change.
Tim
Because for now, you can not change from native packages to quilt, I have two other ways to reduce packages size!
__1__
I tested that all currently supported distributions (Debian from Squeeze, Ubuntu from Lucid) have support for source packages using XZ compression. Switching from bzip2 to XZ can reduce source packages about 12%.
If there are no objections, I can make this change immediately.
__2__
I noticed that although we use bzip2 compression for source packages inside binary packages are still gzip. I checked that there is also possibility to switch compression for binary packages. I tested, that except Lucid is possible to use inside binary packages XZ compression. For Lucid can be used bzip2. The need to use for Lucid a different compression is not a problem. I create rule that automatically selects compression by availability XZ:
DEB_DH_BUILDDEB_ARGS = -- -Z$(shell dpkg-deb --help | grep -q ":.* xz[,.]" \ && echo xz || echo bzip2)
Change from gzip to bzip2 (for Lucid) reduces binary packages by about 12%. Change to XZ (for all others) reduces binary packages by about 25%.
If there are no objections, I add gradually this change to all packages.
On Saturday 06 of October 2012 18:51:23 Slávek Banko wrote:
On Saturday 29 of September 2012 04:05:43 Timothy Pearson wrote:
On Friday 28 of September 2012 17:07:33 Timothy Pearson wrote:
Interesting! Are you going to do this in the R14 packaging tree as well?
I assume that the change native => quilt could be used for the final R14 and certainly for subsequent SRU in R14. In order to use quilt also for the nightly-builds, it requires to modify scripts that you use to prepare packages for nigtly-builds.
For example, it should need to change the version number used for base tarball "orig.tar.bz2" because it is not possible to use dash for a version of "upstream" package on Debian. Instead of 14.0.0-0debian11+r274+pr2~wheezy would have to be used, for example 14.0.0~r274 for the base tarball orig.tar.bz2. And distribution specific version would in this case be: 14.0.0~r274-0debian11~wheezy.
It is therefore a question, whether is now a good time for such a change?
Slavek
As this would require a change of the versioning scheme, now is not a good time for the change.
Tim
Because for now, you can not change from native packages to quilt, I have two other ways to reduce packages size!
__1__
I tested that all currently supported distributions (Debian from Squeeze, Ubuntu from Lucid) have support for source packages using XZ compression. Switching from bzip2 to XZ can reduce source packages about 12%.
If there are no objections, I can make this change immediately.
__2__
I noticed that although we use bzip2 compression for source packages inside binary packages are still gzip. I checked that there is also possibility to switch compression for binary packages. I tested, that except Lucid is possible to use inside binary packages XZ compression. For Lucid can be used bzip2. The need to use for Lucid a different compression is not a problem. I create rule that automatically selects compression by availability XZ:
DEB_DH_BUILDDEB_ARGS = -- -Z$(shell dpkg-deb --help | grep -q ":.* xz[,.]" \ && echo xz || echo bzip2)
Change from gzip to bzip2 (for Lucid) reduces binary packages by about 12%. Change to XZ (for all others) reduces binary packages by about 25%.
If there are no objections, I add gradually this change to all packages.
I see no objection ... nor any other reaction. The decision is entirely up to me?
Slavek --
Dne st 26. září 2012 Calvin Morrison napsal(a):
- Sync'd mirrors - Slavek, Tim, is there enough time to do this in 1
week or should we push release back further?
I casually watching the situation of mirrors. It appears that now are quite good old state (except for one):
1. http://depot-trinity.dotriver.eu/ (winner) new packages copied, old not yet cleared 2. http://mirror.ntmm.org/trinity/ new packages copied, old not yet cleared 3. http://trinity.blackmag.net/ (best) new packages copied, old already cleared
4. http://trinity.netlinux.org.uk/ (very bad) crashed a few times and a large part of the day after crash the synchronization is not performed. At this pace will perform synchronization for many days. It does not seem sensible to wait for this mirror with a press release.
Note: Mirror http://ftp.rezopole.net/tde/ deliberately not mentioning - it does not sync at all.
Slavek --
Le 10.10.2012 17:06, Slávek Banko a écrit :
Dne st 26. září 2012
Calvin Morrison napsal(a):
- Sync'd mirrors - Slavek, Tim, is
there enough time to do this in 1 week or should we push release back further?
I casually watching the situation of mirrors. It appears
that now are
quite good old state (except for one):
http://depot-trinity.dotriver.eu/
(winner) new packages copied, old
not yet cleared
new packages
copied, old not yet cleared
(best)
new packages copied, old already cleared
http://trinity.netlinux.org.uk/
(very bad) crashed a few times and a
large part of the day after crash
the synchronization is not
performed. At this pace will perform
synchronization for many days.
It does not seem sensible to wait for this
mirror with a press
release.
Note: Mirror http://ftp.rezopole.net/tde/ deliberately not
mentioning - it
does not sync at all.
Slavek
Hello,
speaking of mirrors, Tim, can you please add synchronization for the new subfolders on my RPM server ?
Subfolders are:
mga2 (for Mageia 2)
mdv2011.0 (for Mandriva 2011)
opensuse12.2
Some folders are still empty for now, I will populate them soon.
Thanks
Francois
Hello,
speaking of mirrors, Tim, can you please add synchronization for the new subfolders on my RPM server ?
Subfolders are:
mga2 (for Mageia 2)
mdv2011.0 (for Mandriva 2011)
opensuse12.2
Some folders are still empty for now, I will populate them soon.
Thanks
Francois
Done!
Tim
Hi Slavek,
If you have some problems with mirror : depot-trinity.dotriver.eu or ftp.rezopole.net, contact me.
I have send a mail in order to know what happened with ftp.rezopole.net.
Sincerely,
Jean
2012/10/10 Slávek Banko slavek.banko@axis.cz
Dne st 26. září 2012 Calvin Morrison napsal(a):
- Sync'd mirrors - Slavek, Tim, is there enough time to do this in 1
week or should we push release back further?
I casually watching the situation of mirrors. It appears that now are quite good old state (except for one):
http://depot-trinity.dotriver.eu/ (winner) new packages copied, old not yet cleared
http://mirror.ntmm.org/trinity/ new packages copied, old not yet cleared
http://trinity.blackmag.net/ (best) new packages copied, old already cleared
http://trinity.netlinux.org.uk/ (very bad) crashed a few times and a large part of the day after crash
the synchronization is not performed. At this pace will perform synchronization for many days. It does not seem sensible to wait for this mirror with a press release.
Note: Mirror http://ftp.rezopole.net/tde/ deliberately not mentioning - it does not sync at all.
Slavek
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Dne st 26. záÅà 2012 Calvin Morrison napsal(a):
- Sync'd mirrors - Slavek, Tim, is there enough time to do this in 1
week or should we push release back further?
I casually watching the situation of mirrors. It appears that now are quite good old state (except for one):
http://depot-trinity.dotriver.eu/ (winner) new packages copied, old not yet cleared
http://mirror.ntmm.org/trinity/ new packages copied, old not yet cleared
http://trinity.blackmag.net/ (best) new packages copied, old already cleared
http://trinity.netlinux.org.uk/ (very bad) crashed a few times and a large part of the day after crash
the synchronization is not performed. At this pace will perform synchronization for many days. It does not seem sensible to wait for this mirror with a press release.
Note: Mirror http://ftp.rezopole.net/tde/ deliberately not mentioning - it does not sync at all.
Slavek
We are now pretty much ready to release; the two mirrors you mentioned were automatically selected by the system for use and they both appear to be in sync. Does tomorrow (10/11/2012) sound good to all concerned?
In case anyone was curious, I found the source of the extremely slow sync. Our nightly builds are far more popular than I thought; apparently between those and Slavek's PPA (neither of which are on the mirror system) there was not much bandwidth left over for the mirror sync.
Tim
Dne st 10. října 2012 Timothy Pearson napsal(a):
Dne st 26. záÅà 2012 Calvin Morrison napsal(a):
- Sync'd mirrors - Slavek, Tim, is there enough time to do this in
1 week or should we push release back further?
I casually watching the situation of mirrors. It appears that now are quite good old state (except for one):
http://depot-trinity.dotriver.eu/ (winner) new packages copied, old not yet cleared
http://mirror.ntmm.org/trinity/ new packages copied, old not yet cleared
http://trinity.blackmag.net/ (best) new packages copied, old already cleared
http://trinity.netlinux.org.uk/ (very bad) crashed a few times and a large part of the day after
crash the synchronization is not performed. At this pace will perform synchronization for many days. It does not seem sensible to wait for this mirror with a press release.
Note: Mirror http://ftp.rezopole.net/tde/ deliberately not mentioning
- it does not sync at all.
Slavek
We are now pretty much ready to release; the two mirrors you mentioned were automatically selected by the system for use and they both appear to be in sync. Does tomorrow (10/11/2012) sound good to all concerned?
In case anyone was curious, I found the source of the extremely slow sync. Our nightly builds are far more popular than I thought; apparently between those and Slavek's PPA (neither of which are on the mirror system) there was not much bandwidth left over for the mirror sync.
Tim
Tomorrow or today - both sounds good to me :)
Mirrors http://trinity.netlinux.org.uk/ and http://ftp.rezopole.net/tde anyway not have a chance to be ready, so these do not take into consideration. Tomorrow has the advantage that the mirrors could have removed the old packages. However, it probably is not so important.
Note: Interesting information about the load line.
Slavek --
Hi all,
Just for say :
Note: Mirror http://ftp.rezopole.net/tde/ deliberately not mentioning
- it does not sync at all.
I will be good. A trainee make a mistake ....
The rsync is launched.
Sorry.
Sincerely,
Jean
2012/10/10 Slávek Banko slavek.banko@axis.cz
Dne st 10. října 2012 Timothy Pearson napsal(a):
Dne st 26. zářà 2012 Calvin Morrison napsal(a):
- Sync'd mirrors - Slavek, Tim, is there enough time to do this in
1 week or should we push release back further?
I casually watching the situation of mirrors. It appears that now are quite good old state (except for one):
http://depot-trinity.dotriver.eu/ (winner) new packages copied, old not yet cleared
http://mirror.ntmm.org/trinity/ new packages copied, old not yet cleared
http://trinity.blackmag.net/ (best) new packages copied, old already cleared
http://trinity.netlinux.org.uk/ (very bad) crashed a few times and a large part of the day after
crash the synchronization is not performed. At this pace will perform synchronization for many days. It does not seem sensible to wait for this mirror with a press release.
Note: Mirror http://ftp.rezopole.net/tde/ deliberately not mentioning
- it does not sync at all.
Slavek
We are now pretty much ready to release; the two mirrors you mentioned were automatically selected by the system for use and they both appear to be in sync. Does tomorrow (10/11/2012) sound good to all concerned?
In case anyone was curious, I found the source of the extremely slow sync. Our nightly builds are far more popular than I thought; apparently between those and Slavek's PPA (neither of which are on the mirror system) there was not much bandwidth left over for the mirror sync.
Tim
Tomorrow or today - both sounds good to me :)
Mirrors http://trinity.netlinux.org.uk/ and http://ftp.rezopole.net/tde anyway not have a chance to be ready, so these do not take into consideration. Tomorrow has the advantage that the mirrors could have removed the old packages. However, it probably is not so important.
Note: Interesting information about the load line.
Slavek
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-
Calvin Morrison -
Darrell Anderson -
François Andriot -
Jean Milot -
Robert Xu -
Slávek Banko -
Timothy Pearson