Hi to all, I'm not sure if everyone is aware of this, but Chris Nighswonger (3.2.x mantainer) will release 3.2.1 at 22 of November. And 3.2.2 is planned at 22 oF Dec., etc. One release evry month around 22 of the month. To keep transaltion in sync I suggest: -- Release Day - 8 day: TM update the site for traslation [http://translate.koha-community.org/] and all .po files. -- Translators works or send file until Release Day - 2 day -- RM of 3.2.x uses te version that is present on the site. What do you think about this warkflow ? -- Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci qaunto tra AT con @)
Zeno++ I tested a lot of translation bugs today, that are solved in 3.2.1. So there are some new and fuzzy strings now that require translating or resubmitting. Updating the .po files a short time before the bugfix releases is a good idea in my opinion. Perhaps we can do an update some time soon - so people can already start and update their 3.2.1 installations using the .po files from pootle.
-----Original Message----- From: koha-translate-bounces@lists.koha-community.org [mailto:koha- translate-bounces@lists.koha-community.org] On Behalf Of Zeno Tajoli Sent: Tuesday, November 16, 2010 4:32 PM To: koha-translate@lists.koha-community.org; cnighswonger@foundations.edu Subject: [Koha-translate] A timetable proposal for new 3.2.x releases
Hi to all,
I'm not sure if everyone is aware of this, but Chris Nighswonger (3.2.x mantainer) will release 3.2.1 at 22 of November.
And 3.2.2 is planned at 22 oF Dec., etc. One release evry month around 22 of the month.
To keep transaltion in sync I suggest: -- Release Day - 8 day: TM update the site for traslation [http://translate.koha-community.org/] and all .po files.
-- Translators works or send file until Release Day - 2 day
-- RM of 3.2.x uses te version that is present on the site.
What do you think about this warkflow ?
-- Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci qaunto tra AT con @) _______________________________________________ Koha-translate mailing list Koha-translate@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate
website: www.koha-community.org git: git.koha-community.org bugs: bugs.koha-community.org
Hi all, On Tue, Nov 23, 2010 at 10:18 AM, Fischer, Katrin <Katrin.Fischer@bsz-bw.de>wrote:
Zeno++
I tested a lot of translation bugs today, that are solved in 3.2.1. So there are some new and fuzzy strings now that require translating or resubmitting.
Updating the .po files a short time before the bugfix releases is a good idea in my opinion.
Perhaps we can do an update some time soon - so people can already start and update their 3.2.1 installations using the .po files from pootle.
My understanding of the process is that translation updates are finally submitted as patches for inclusion in the main repo. It is also my understanding that the translation manager is responsible for submitting these patches. If my understanding is correct, then the failure to submit the necessary patches for inclusion in the main repo would result in their not being included in the maintenance release. In light of that, I'm wondering if/when Frédéric plans to have the new translate.kc.org site up and operational? I cannot speak for Chris C., but I'm guessing that his time for work on translation stuff is limited now that he is in the role of release manager. I think that Zeno's suggested schedule is workable and good, from my standpoint. However, as a rule, changes will need to be submitted and in HEAD two days prior to the announced release date for inclusion in the maintenance release. If you as a translator see this is not happening, please feel free to contact the translation manager. Outstanding, mitigating, unforeseen, and <your-favorite-term-here> factors will certainly be considered and even accommodated as they occur. Kind Regards, Chris
My understanding of the process is that translation updates are finally submitted as patches for inclusion in the main repo. It is also my understanding that the translation manager is responsible for submitting these patches. If my understanding is correct, then the failure to submit the necessary patches for inclusion in the main repo would result in their not being included in the maintenance release.
To be confirmed with Chris, but I suppose you're correct. I plan to have two branches on a git repo, one 'translation' for master and another one named 'translation-3.2' for stable branch. You'll be able to pull directly .po files from the stable branch.
In light of that, I'm wondering if/when Frédéric plans to have the new translate.kc.org site up and operational? I cannot speak for Chris C., but I'm guessing that his time for work on translation stuff is limited now that he is in the role of release manager.
I will have installed tomorrow a dedicated server for Pootle. So the switch can be done quickly from now. -- Frédéric
2010/11/24 Frédéric DEMIANS <f.demians@tamil.fr>:
My understanding of the process is that translation updates are finally submitted as patches for inclusion in the main repo. It is also my understanding that the translation manager is responsible for submitting these patches. If my understanding is correct, then the failure to submit the necessary patches for inclusion in the main repo would result in their not being included in the maintenance release.
To be confirmed with Chris, but I suppose you're correct. I plan to have two branches on a git repo, one 'translation' for master and another one named 'translation-3.2' for stable branch. You'll be able to pull directly .po files from the stable branch.
Sounds like a fine idea.
In light of that, I'm wondering if/when Frédéric plans to have the new translate.kc.org site up and operational? I cannot speak for Chris C., but I'm guessing that his time for work on translation stuff is limited now that he is in the role of release manager.
I will have installed tomorrow a dedicated server for Pootle. So the switch can be done quickly from now.
Excellent :) Let me know if you need anything from me Chris
And 3.2.2 is planned at 22 oF Dec., etc. One release evry month around 22 of the month.
To keep transaltion in sync I suggest: -- Release Day - 8 day: TM update the site for traslation [http://translate.koha-community.org/] and all .po files.
-- Translators works or send file until Release Day - 2 day
-- RM of 3.2.x uses te version that is present on the site.
It works for me. Could we fix the schedule now for the next release? I propose: - Dec 15th. I update all .po files with last strings. I send a message on this list when it's done. Translators start working on updating their translations. - Dec 20. Translation is frozen. I update my repo with update .po files and send them on a git repository. I send a announce on koha-patches and koha-translate lists. - Dec 22. Chris N. pull last .po files and integrate them to its 3.2.x release. -- Frédéric DEMIANS
2010/12/6 Frédéric DEMIANS <f.demians@tamil.fr>
And 3.2.2 is planned at 22 oF Dec., etc. One release evry month around 22 of the month.
To keep transaltion in sync I suggest: -- Release Day - 8 day: TM update the site for traslation [http://translate.koha-community.org/] and all .po files.
-- Translators works or send file until Release Day - 2 day
-- RM of 3.2.x uses te version that is present on the site.
It works for me. Could we fix the schedule now for the next release?
I propose:
- Dec 15th. I update all .po files with last strings. I send a message on this list when it's done. Translators start working on updating their translations. - Dec 20. Translation is frozen. I update my repo with update .po files and send them on a git repository. I send a announce on koha-patches and koha-translate lists. - Dec 22. Chris N. pull last .po files and integrate them to its 3.2.x release.
This is ok by me as well. So 3.2.2 will enter a string freeze on Dec. 15 with only patch not changing/adding strings will be applied after that date. The release will be on Dec. 22. Kind Regards, Chris
participants (5)
-
Chris Cormack -
Chris Nighswonger -
Fischer, Katrin -
Frédéric DEMIANS -
Zeno Tajoli