[hugin-ptx] Re: Status of branches: I'm lost (Was: What's in a Version Number?)
Oskar Sander wrote: Nice, I like the description on Development cycle and Release cycle you have added. thanks, Oskar. It's work in progress. http://wiki.panotools.org/Development_of_Open_Source_tools has been massively overhauld yesterday and is likely to still see many changes. Feel free to add to it. Where do I look in the wiki to see what the active release branches are, description and status of the branches, who the release managers are and his/her comments? Is it intended to be under the link below or is it already somewhere else? How do you define an active release branch? some of the information changes too often. The effort of maintaining it on a Wiki has to be waged against using the time for other project tasks. Just follow this mailing list and you will know who the release managers are and read their comments. assigning formal responsibilities does not work in the context of this project. see the history of that document for build chain responsible in the section http://wiki.panotools.org/Development_of_Open_Source_tools#Supported_Platforms The build chain documentation works quite well without formal responsibilities assigned . Whoever feels the itch takes the leadership and scratch it. http://wiki.panotools.org/Development_of_Open_Source_tools#Specific_revisions These are just a few pointer in the flow of time / revisions. If you want more detail, you will need to follow the revision logs. I've linked them there. Interest rises and ebbs depending on the current momentum. These specific revisions become outdated as development continues and it takes a considerable effort to keep them updated. Consider them as entry points to make the newbie building experience less frustrating, but they are not intended to be up to date. Yuv --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Status of branches: I'm lost (Was: What's in a Version Number?)
Hi Thomas, T. Modes wrote: I think the bug is in rev 4289. I assume you runned extract- messages.sh. But in this run the ressource files (xrc) were not considered. (The commented out strings are mostly from the xrc files) Maybe the program wxrc (utils of wxwidgets) is missing or not compiled which is needed by extract-messages.sh. thanks for the feedback. fixed. I don't use any other language than English for the user interface so I could not check. Can somebody confirm? you are also right about the cause of the problem. I've updated http://wiki.panotools.org/Hugin_translation_guide#Adding_new_strings accordingly. SVN 4308 for trunk SVN 4309 for releases/2009.2 thank you also for your fixes. Yuv --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Status of branches: I'm lost (Was: What's in a Version Number?)
Nice, I like the description on Development cycle and Release cycle you have added. Where do I look in the wiki to see what the active release branches are, description and status of the branches, who the release managers are and his/her comments? Is it intended to be under the link below or is it already somewhere else? http://wiki.panotools.org/Development_of_Open_Source_tools#Specific_revisions Cheers /O 2009/8/30 Yuval Levy goo...@levy.ch [0] http://wiki.panotools.org/Development_of_Open_Source_tools#Release_Cycle [1] http://sourceforge.net/tracker/?func=group_id=77506atid=550441status=1 [2] http://wiki.panotools.org/Development_of_Open_Source_tools#Branching_Out_For_Release -~--~~~~--~~--~--~--- -- /O --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Status of branches: I'm lost (Was: What's in a Version Number?)
On 30 авг, 19:27, Yuval Levy goo...@levy.ch wrote: The plan is to go live with this stable ASAP, with what is in it now. the mandatory condition to go live is: 1. it builds on the main supported platforms (Linux/Windows/OSX) 2. it does not break existing functionality from the previous release (unless the breakage is intentional) nice to have: 1. fixes for the priority 9 open bugs in the tracker [1] 2. other bug fixes 3. translations So translators can actually still commit translation updates to ../ releases/2009.2? How much time do translators have? Alexandre --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Status of branches: I'm lost (Was: What's in a Version Number?)
On 31 авг, 16:06, Alexandre Prokoudine alexandre.prokoud...@gmail.com wrote: So translators can actually still commit translation updates to ../ releases/2009.2? How much time do translators have? And releases/2009.2 doesn't build anyway: http://pastebin.com/m2ed0e86a Alexandre --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Status of branches: I'm lost (Was: What's in a Version Number?)
Alexandre Prokoudine wrote: So translators can actually still commit translation updates to ../ releases/2009.2? How much time do translators have? Translators have all the time they want :) The goal of the new process is to decouple release from development; and translation is a kind of development. Translators get the same freedom as developers: you can do whatever you want in trunk; and you can help polishing the release in releases/2009.2 The only thing to pay attention to is that over time the *.po files in trunk will differ from the *.po files in the release codeline; and that changes need to be kept in sync. This could be easily achieved with a string freeze in releases/2009.2, but I would hate to do that. I'd rather move fast forward on the release, and in the meantime monitor the two codelines and sync when necessary (i.e. when the translator or developer has not done it). For release, the criteria for translation is the same as for functionality: if there is no (known) regression, it's good to go. If translations are added/polished after release, they will surely go into the next release and if there is enough support we can release a patch version (e.g. 2009.2.0 is released with translations as-is and 2009.2.1 is released with the improved translations that have arrived after 2009.2.0 was released). Yuv --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Status of branches: I'm lost (Was: What's in a Version Number?)
Hi Yuv, the translation does not work correctly. Only a few strings get translated. Most strings of the GUI are in english independed of the choosen language. When looking into the po files you can see that many many strings are commented out. This affects all languages and needs to fixed. I think the bug is in rev 4289. I assume you runned extract- messages.sh. But in this run the ressource files (xrc) were not considered. (The commented out strings are mostly from the xrc files) Maybe the program wxrc (utils of wxwidgets) is missing or not compiled which is needed by extract-messages.sh. Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Status of branches: I'm lost (Was: What's in a Version Number?)
Hi Harry, Harry van der Wolf wrote: I'm still lost. sorry for the confusion. my fault, I have not made the official announcement yet (waiting for Bruno to confirm). To what branch do I now have to apply patches/changes? 2009.2 has been created a couple of days ago (or so). Thereby, the standard trunk has become 2009.3 being the unstable development trunk. 2009.2 was created nine hours ago. the how and why is all explained at [0]. The only thing I did not do yet is announce because I want my tarball to be verified by Bruno who is mentoring me in the process. Now, when I apply patches I will do that to the trunk, thereby to the unstable development version (do I?). I've seen your commits to trunk. trunk is development, so yes, you committed to the unstable development version which is synonymous to trunk. With the new release process there is no trunk freeze. Committer need not worry about release branches. In fact, now that 2009.2 is branched out, one of our GSoC students could start integrating their code in trunk. Any volunteers? Is there now a super admin who decides what goes into 2009.2 (being the stable one). If so: Is there a planning when we going life with this stable one and what's in it? there is no super admin, or at least we have not discussed it. there is a release manager, and for 2009.2 I am that person. I took ownership/responsibility for the release by branching out. The plan is to go live with this stable ASAP, with what is in it now. the mandatory condition to go live is: 1. it builds on the main supported platforms (Linux/Windows/OSX) 2. it does not break existing functionality from the previous release (unless the breakage is intentional) nice to have: 1. fixes for the priority 9 open bugs in the tracker [1] 2. other bug fixes 3. translations W.r.t. to the stable one and when not having a super admin: Do I have to apply stable changes like the dutch translation from this morning and a Xcode related Hugin version upgrade to both trunks? use common sense: if it is a bug fix or a translation, doing it to both is nice. if it is a feature, add it to trunk only. part of my responsibility as release manager is to make sure that changes applied to trunk only and that are relevant for the release are applied to the release branch as well. and after the release i will make sure that changes applied to the release branch only and that are relevant to trunk will be applied there too. W.r.t. the latter: I set versioning for XCode to 2009.3 (the trunk): I now see that this patch has also been applied to the stable trunk 2009.2, but that's not correct, which means it's not a stable change. oh, stupid me. I just blindly copy/pasted the change without thinking. Fixed it. Please give some advice. I see the changes you did and tried to document them (steps 3.c / 4.c in [2]). I have no Mac, so I can't verify if I am correct or if other things need to be done. Feel free to update the wiki document. A completely and utterly lost, Harry I apologize again for the confusion. If you have specific questions, ask. The goal is to document everything in [0] so that nobody gets lost in the future. Yuv [0] http://wiki.panotools.org/Development_of_Open_Source_tools#Release_Cycle [1] http://sourceforge.net/tracker/?func=group_id=77506atid=550441status=1 [2] http://wiki.panotools.org/Development_of_Open_Source_tools#Branching_Out_For_Release --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Status of branches: I'm lost (Was: What's in a Version Number?)
Harry van der Wolf wrote: Am I that impatient? ;-) you? no, me! I hoped to get the beta release officially out this weekend but it did not happen. Maybe tomorrow. I see the changes you did and tried to document them (steps 3.c / 4.c in [2]). I have no Mac, so I can't verify if I am correct or if other things need to be done. Feel free to update the wiki document. I'll try to do so the coming days. Need to check on the libpano status though. thanks. yes, we'll need a libpano release soon too. Thanks for all the explanation. I now have this warm and comfortable community feeling back. change can have side effects, but they are all temporary and usually after the change everybody feels better again :-) there will be a change for snapshot builders: to help polishing the release they will have to build the snapshots from the release codeline instead of the trunk codeline. details will follow after the official beta 1 announcement. Yuv --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
