few more questions about being part of extragear

[robbystephenson]

Hi,

I had a few more questions about integrating Tellico into the Extragear
world. I really appreciate all the help I've been getting figuring out the
KDE SVN involvement, along with all the new translation work. It's been
really exciting for me to see all that.

* What do I need to do to get some info on the extragear website, notably
http://extragear.kde.org/apps/tellico? I'm guessing there's something in the
KDE SVN tree somewhere that I need to edit, but I didn't want to go poking
around too much.

* is there a process for announcing new releases? I plan to make releases
separate from the main KDE releases. I wasn't sure if there was anything in
particular to being extragear that I needed to be aware of.

* is there a policy on tagging and branching that I should read? If I do a
beta or pre-release, should I tag and where should I tag? I also need help
figuring out that stable tag for extragear. I read back through the mailing
list and I couldn't quite figure out what the stable tag implied.

* I'm guessing it's a big help for the translators to know about upcoming
string freezes and releases, right? If I email kde-i18n-doc, that's
sufficient?

Thanks!
Robby
_______________________________________________
Kde-extra-gear mailing list
Kde-extra-gear@...
https://mail.kde.org/mailman/listinfo/kde-extra-gear

Robby Stephenson wrote:
> Hi,
>
> I had a few more questions about integrating Tellico into the Extragear
> world. I really appreciate all the help I've been getting figuring out the
> KDE SVN involvement, along with all the new translation work. It's been
> really exciting for me to see all that.

Welcome aboard :).


> * What do I need to do to get some info on the extragear website, notably
> http://extragear.kde.org/apps/tellico? I'm guessing there's something in the
> KDE SVN tree somewhere that I need to edit, but I didn't want to go poking
> around too much.

Check out /trunk/www/areas/extragear/

IIRC you need some privileges added to your SVN account
to be able to edit those files.


> * is there a process for announcing new releases? I plan to make releases
> separate from the main KDE releases. I wasn't sure if there was anything in
> particular to being extragear that I needed to be aware of.

You can have the release team package things for you along-
side KDE releases, or make your own releases. Here's the
checklist I use for the latter, i.e. when I make Konversa-
tion and Yakuake releases:

x   select translations
x   adjust codebase for release
x   generate tarball
x   do build tests
x   tag
x   adjust codebase for next dev cycle
x   add new version in bugzilla
x   upload tarball to berlios
x   news entry at berlios
x   news entry at sourceforge
x   update website
x   update extragear website app info
x   update kde-apps entry
x   mail kde-announce-apps & konversation-devel
x   update irc channel topic
n   update wikipedia en & de
n   update freshmeat
nnn update screenshots (website, kde-apps, freshmeat)
n   update ohloh (app icon/logo)
(x = done; n = not applicable this time around)

The specific example is for Konversation 1.2-alpha4, the
most recent release I did.

I do the "select translations" step with a self-written
script that gets all the available translations for an
Extragear app from IRC and can then tell me which langs
have translations available at all or not, and which meet
a specified percentage of coverage. It can also run a
few tests, although the need for those should be elimi-
nated these days with the pre-commit hooks in the SVN
server performing tests as well and rejecting faulty
translation commits (afaik).

I usually ship all translations with have 65% complete-
ness or higher.

For the "add new version in bugzilla" step your Bug-
zilla account will need to have privileges to edit
products added.

I use kdesdk's create_tarball.rb script for the "ge-
nerate tarball" step. This is also what the release
team uses.

(The old similar "svn2dist" bash script we had in the
KDE 3 times was a bit niftier in that you could hand
it a list of translation languages to omit in genera-
ting the tarball, so I could basically hand it the
output of my aforementioned script, the list of langs
with no or insufficient translations. With the new
script, create_tarball.rb, you need to do that by
hand / a second self-written script.)


> * is there a policy on tagging and branching that I should read? If I do a
> beta or pre-release, should I tag and where should I tag? I also need help
> figuring out that stable tag for extragear. I read back through the mailing
> list and I couldn't quite figure out what the stable tag implied.

I tag any Yakuake and Konversation releases - alphas,
betas, RCs - in /tags/appname, e.g.:

http://websvn.kde.org/tags/yakuake/

Yakuake and Konversation so far have made releases
exclusively from trunk. Other Extragear apps make
use of a stable branch in /branches/stable/. Basi-
cally, if you make an 1.0 release and start deve-
loping your radical new 2.0 in trunk it's probably
useful to have a stable branch to make a 1.0.1 from.

I've so far ignored the stable tag and no one has
ever complained.


> * I'm guessing it's a big help for the translators to know about upcoming
> string freezes and releases, right? If I email kde-i18n-doc, that's
> sufficient?

Yes, you need to announce your string freeze and up-
coming release dates to kde-i18n-doc. Give them two
weeks before a release at least, or more depending
on the number of new/changed strings. However you
should also update this table on the Techbase wiki:

http://techbase.kde.org/Schedules/Extragear


> Thanks!
> Robby

--
Regards,
Eike Hein, hein@...
_______________________________________________
Kde-extra-gear mailing list
Kde-extra-gear@...
https://mail.kde.org/mailman/listinfo/kde-extra-gear

Eike Hein wrote:
> I've so far ignored the stable tag and no one has
> ever complained.

... and considering that with the exception of
kphotoalbum, no stable tag has changed in the
last 20 months, the same appears to be true for
most Extragear devs.


--
Regards,
Eike Hein, hein@...
_______________________________________________
Kde-extra-gear mailing list
Kde-extra-gear@...
https://mail.kde.org/mailman/listinfo/kde-extra-gear

Eike Hein wrote:
> I tag any Yakuake and Konversation releases - alphas,
> betas, RCs - in /tags/appname, e.g.:
>
> http://websvn.kde.org/tags/yakuake/

Sorry, forgot to add that afair you need to ask a
sysadmin to create a new dir for you in /tags.


--
Regards,
Eike Hein, hein@...
_______________________________________________
Kde-extra-gear mailing list
Kde-extra-gear@...
https://mail.kde.org/mailman/listinfo/kde-extra-gear

[Tom Albers]

At Monday 03 August 2009 05:26, you wrote:
> (The old similar "svn2dist" bash script we had in the
> KDE 3 times was a bit niftier in that you could hand
> it a list of translation languages to omit in genera-
> ting the tarball, so I could basically hand it the
> output of my aforementioned script, the list of langs
> with no or insufficient translations. With the new
> script, create_tarball.rb, you need to do that by
> hand / a second self-written script.)

Hehe, when you don't tell me, it will never be added ;-)

Anyhow, do you need to feed it a list of languages or a setting which only includes languages with a percentage translated?

Best,

Toma

_______________________________________________
Kde-extra-gear mailing list
Kde-extra-gear@...
https://mail.kde.org/mailman/listinfo/kde-extra-gear

Tom Albers wrote:
> Hehe, when you don't tell me, it will never be added ;-)

Actually I did tell you, sorta, but in the wrong way - I
asked if you'd be ok with *me* adding such a feature (to
which you said "yes"), but then never got around to it.
So in the end, still my bad :).


> Anyhow, do you need to feed it a list of languages or a setting which only includes languages with a percentage translated?

With svn2dist, you fed it a list of languages to omit,
which I'm set up to produce with my own translations
script. But that's not the case for everybody, I guess,
and with the need for the testing my script used to do
(i.e. run msgfmt -c and check_po_files) now apparently
gone, it just comes down to wanting to do that coverage
percentage threshold. So a setting for the percentage
would float my boat and make my other script as well
as an option to feed a list unnecessary from my end.


> Best,
>
> Toma

--
Regards,
Eike Hein, hein@...
_______________________________________________
Kde-extra-gear mailing list
Kde-extra-gear@...
https://mail.kde.org/mailman/listinfo/kde-extra-gear

[robbystephenson]

Thats a lot of infor and a big help, thanks Eike.

Robby

On Sunday 02 August 2009, Eike Hein wrote:

> You can have the release team package things for you along-
> side KDE releases, or make your own releases. Here's the
> checklist I use for the latter, i.e. when I make Konversa-
> tion and Yakuake releases:
>
> x   select translations
> x   adjust codebase for release
> x   generate tarball
> x   do build tests
> x   tag
> x   adjust codebase for next dev cycle
> x   add new version in bugzilla
> x   upload tarball to berlios
> x   news entry at berlios
> x   news entry at sourceforge
> x   update website
> x   update extragear website app info
> x   update kde-apps entry
> x   mail kde-announce-apps & konversation-devel
> x   update irc channel topic
> n   update wikipedia en & de
> n   update freshmeat
> nnn update screenshots (website, kde-apps, freshmeat)
> n   update ohloh (app icon/logo)
> (x = done; n = not applicable this time around)

Thats a lot of info and a big help, thanks Eike.

Robby

_______________________________________________
Kde-extra-gear mailing list
Kde-extra-gear@...
https://mail.kde.org/mailman/listinfo/kde-extra-gear