[bt-devel] BibleTime 2.0.beta3 released - i18n freeze - preliminary release schedule for discussion

[Jonathan Marsden]

Gary Holmlund wrote:

>> Maybe we should wait a bit longer between the rc and the final? We are
>> lucky to have a good packaging support at least for .deb packages and
>> it could be useful to get the packages into the repositories. Then the
>> ordinary end users could use it and possibly find critical bugs before
>> the final release. Can Jonathan give us any estimation about how soon
>> the rc packages would be in the repos after the source release?

Well, it depends how busy I am :)  I've been known to package things on
the day of release, but I'm not about to guarantee that!

I think I can probably do it within two or three days, unless something
unexpected happens that eats up my time right when the release happens.

That is, I can package it and get it into the PPAs (mine and the
~pkgcrosswire team one) that fast.  Actually getting it into "real"
repositories takes longer, usually I can get something into Debian
experimental or Debian unstable about a week after I create the packages
(Roberto has to quality check the packages and then upload them, and
then the automated systems have to build them and move them around...).

A week or more between RC and final would seem better to me, if that is
practical.  I don't know what the time constraints the project has are.

> Regarding the configure.svg problem. The problem can be demonstrated in
> a tiny Qt program written from scratch. It is clear that all the
> programs that fail to display it correctly are based on Qt4. I don't
> know if the is a Qt bug or a problem with the icon and Qt is less
> tolerant than other programs. The only choice I see is to recreate the
> icon. I am not very proficient with creating svg icons. Is there anyone
> else that knows how to do it?

I'm similarly graphics-challenged, but it might be worth playing with
"open configure.svg with Inkscape, export as .EPS.  Import EPS file into
OpenOffice Draw, and export as SVG.  Test the resulting "new" SVG."
kinds of processes.  Repeat for other vector graphics programs if you
have some more available!  Different graphics programs export
differently, and so this kind of "silly" double conversion may be enough
to remove whatever the problem SVG code is that is tripping up Qt4.
Plus, it can be done without being able to draw :)

Jonathan