Thanks, RAOF, come back soon! David
On Thu, Feb 26, 2009 at 9:38 AM, Jason Smith <[email protected]> wrote: > > Thank you RAOF, good luck with the move! > > On Thu, 2009-02-26 at 18:55 +1100, Christopher James Halse Rogers wrote: > > Hello all! > > > > I'm moving this weekend, and one of the consequences of this is that > > I'll need to set up internet access at the new place. This will take > > some time - apparently, two to four weeks(!). During this time, I'll > > have only sporadic internet access. > > > > I will still be checking my email, but I won't be idling on IRC quite as > > much! > > > > In the interest of ensuring my absence doesn't cause too much of a > > problem, I'll try to document all the steps required to make a release: > > > > a) Download translations from Launchpad[1]. Copy them into the po/ > > directory, then mass-rename them to strip the prefix. > > > > b) Bump the version in configure.ac. You don't need to do this this > > time, the version is already 0.8.1. > > > > c) Ensure it builds sanely: > > - The most important tool here is "make distcheck". This will build a > > tarball, extract the tarball, and do an out-of-tree build, then run some > > sanity checks (translatable files missing from po/POTFILES.in, etc). If > > this works it's a pretty good indication that the tarball will build on > > someone else's system - you haven't got some files in your working tree > > that aren't in the tarball, etc. If it doesn't pass "make distcheck", > > don't release - it probably won't build for someone. > > > > Common faults here are: > > * missing files from POTFILES.in. To fix this, "grep Catalog.GetString > > **/*.cs >> po/POTFILES.in", and remove the duplication. > > > > * Files missing from EXTRA_DIST somewhere. This shouldn't really happen > > with our new build system; all that voodoo is wrapped up in > > build.rules.mk. > > > > d) Upload the tarball to Launchpad. This is not necessarily obvious: > > - Uploads *have* to be associated with a release, which *has* to be > > associated to a series. We probably want to use the "0.8" series[2], > > then hit "register a release"[3]. > > - Now you've got a release, you'll want to go to the release page, and > > hit the "Add download file" button. If you've got a GPG key in the > > strong set (or otherwise well knows), sign it - the page tells you how. > > - Hit "upload", and you're done. > > > > There we go; the potted guide to making a GNOME Do release. > > > > > > [1] > > https://translations.edge.launchpad.net/do/trunk/+pots/gnomedo/+export > > > > [2] https://edge.launchpad.net/do/0.8 > > [3] https://edge.launchpad.net/do/0.8/+addrelease > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GNOME Do" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/gnome-do?hl=en -~----------~----~----~----~------~----~------~--~---
