Hello, Since most parts of the merged desktop work well, maybe we should have a release plan? Here are some problems: 1. Creating tarballs: Do we need some cmake macros to hellp create tarballs? (something like create_portable_header.cmake or create_pkgconfig) 2. How to give the components version numbers? Are there any rules? 3. The translation workflow? Transifex, pootle, or both? 4. Release schedule? 5. Luis is working on building all of the components with a toplevel CMakeLists.txt file. Are there any progress? Or, are there anything needs to be fixed in the autotools stuff?
About the translation part, I'd like to ask Martin Baggie for details. How exactly should pootle work with the xml *.ts files? With gettext files, we only touch the template *.pot file and let you merge the changes to other *.po files. With Qt *.ts xml files, how to keep this work flow? Should we only touch the template *.ts file and leave the task of merging the changes to *.ts files of different languages to you? By default the Qt linguist rules generated by cmake will update *.ts files of all languages at the same time. To avoid conflicting with pootle, we'll need to avoid committing other *.ts files and only commit the template *.ts file to git. Then, you need to update the other *.ts files by merging the new changes in the template. It seems that the command "lconvert" does this, but doing this manually can be time-consuming. Do you have better workflow? Thank you all. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ Lxde-list mailing list Lxde-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxde-list
