You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by "Marcus (OOo)" <ma...@wtnet.de> on 2014/06/06 21:34:45 UTC
[RELEASE PLANNING] New release planning template in the Wiki
https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Planning+Template
As promised some time ago I've now created a schedule plan for a new
release.
At first view it may look too detailed but IMHO exactly this is the
advantage that nothing is forgotten and there is a kind of checklist
public at a central place that everybody can find. Because it's a Wiki
page everybody can correct or add things that were forgotten but
important to know.
Maybe obvious but please do not fill this plan but copy & paste and
create a new "Release Planning AOO X.Y.Z" wiki page when it is time for
a new release.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE PLANNING] New release planning template in the Wiki
Posted by "Marcus (OOo)" <ma...@wtnet.de>.
Am 06/19/2014 08:40 AM, schrieb Andrea Pescetti:
> Marcus (OOo) wrote:
>> Am 06/07/2014 02:32 PM, schrieb Marcus (OOo):
>>> The 3 phases came from the reality in the past - at I remeber this way.
>>> We made some last minutes changes into the build, even when it was after
>>> the deadline. ...
>> I've changed this and now there is only 1 translation phase directly
>> after feature + string freeze.
>> I've also added a sentence that translation phase means strings *and*
>> dictionaries.
>> Does it look better now?
>
> Thanks, I think it's perfect now. Or at least, this is how we want it to
> be... then in the past we made many exceptions, but if we manage to have
> clear translation (and in general, l10n-related) deadlines it will be
> simpler.
yes, the exceptions will come anyway - even when Juergen don't want to
hear (read) this. ;-)
But this is no reason to document it. This became clear to me when
looking again on the table.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE PLANNING] New release planning template in the Wiki
Posted by Jürgen Schmidt <jo...@gmail.com>.
On 19/06/14 08:40, Andrea Pescetti wrote:
> Marcus (OOo) wrote:
>> Am 06/07/2014 02:32 PM, schrieb Marcus (OOo):
>>> The 3 phases came from the reality in the past - at I remeber this way.
>>> We made some last minutes changes into the build, even when it was after
>>> the deadline. ...
>> I've changed this and now there is only 1 translation phase directly
>> after feature + string freeze.
>> I've also added a sentence that translation phase means strings *and*
>> dictionaries.
>> Does it look better now?
>
> Thanks, I think it's perfect now. Or at least, this is how we want it to
> be... then in the past we made many exceptions, but if we manage to have
> clear translation (and in general, l10n-related) deadlines it will be
> simpler.
well we had this deadlines in the past as well but they were ignored or
people wasn't aware of them because they ready the l10n list only. So it
was more a communication problem ;-)
Juergen
>
> Regards,
> Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE PLANNING] New release planning template in the Wiki
Posted by Andrea Pescetti <pe...@apache.org>.
Marcus (OOo) wrote:
> Am 06/07/2014 02:32 PM, schrieb Marcus (OOo):
>> The 3 phases came from the reality in the past - at I remeber this way.
>> We made some last minutes changes into the build, even when it was after
>> the deadline. ...
> I've changed this and now there is only 1 translation phase directly
> after feature + string freeze.
> I've also added a sentence that translation phase means strings *and*
> dictionaries.
> Does it look better now?
Thanks, I think it's perfect now. Or at least, this is how we want it to
be... then in the past we made many exceptions, but if we manage to have
clear translation (and in general, l10n-related) deadlines it will be
simpler.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE PLANNING] New release planning template in the Wiki
Posted by "Marcus (OOo)" <ma...@wtnet.de>.
Am 06/07/2014 02:32 PM, schrieb Marcus (OOo):
> Am 06/07/2014 02:03 PM, schrieb Andrea Pescetti:
>> On 06/06/2014 Marcus (OOo) wrote:
>>> https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Planning+Template
>>>
>>>
>>> As promised some time ago I've now created a schedule plan for a new
>>> release.
>>
>> This will surely be helpful. I made some changes, but I'm confused about
>> the three translation phases. For sure this part is not reflecting
>> reality, we don't have three translation phases. The process is as
>> follows:
>> - We set a deadline for new translations to reach 100%
>> - We set a deadline for existing translations to be fixed in Pootle
>> - We set a deadline for updating/integrating dictionaries
>> - We currently don't set deadlines for the Release notes, but we could
>>
>> The three deadlines can well be the same. And any action requiring code
>> change must be requested in Bugzilla (so: if fixes are made in the
>> French translation, volunteers will open an issue to integrate the
>> fixes; same for any other actions).
>>
>> A translation never "starts": it is always open, and volunteers can ask
>> for import from Pootle when necessary.
>>
>> I don't know how to put this process in the current version of the plan.
>> What did you have in mind with the three translation phases? A full
>> import at the end of each phase? We are not doing that and we won't so
>> long as we use the current technology.
>
> The 3 phases came from the reality in the past - at I remeber this way.
> We made some last minutes changes into the build, even when it was after
> the deadline.
>
> So, IMHO we should count with this. That was the reason for the 3
> different entries.
>
> Of course this can be changed. It was just a first try to create a plan.
I've changed this and now there is only 1 translation phase directly
after feature + string freeze.
I've also added a sentence that translation phase means strings *and*
dictionaries.
Does it look better now?
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE PLANNING] New release planning template in the Wiki
Posted by "Marcus (OOo)" <ma...@wtnet.de>.
Am 06/07/2014 02:03 PM, schrieb Andrea Pescetti:
> On 06/06/2014 Marcus (OOo) wrote:
>> https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Planning+Template
>>
>> As promised some time ago I've now created a schedule plan for a new
>> release.
>
> This will surely be helpful. I made some changes, but I'm confused about
> the three translation phases. For sure this part is not reflecting
> reality, we don't have three translation phases. The process is as follows:
> - We set a deadline for new translations to reach 100%
> - We set a deadline for existing translations to be fixed in Pootle
> - We set a deadline for updating/integrating dictionaries
> - We currently don't set deadlines for the Release notes, but we could
>
> The three deadlines can well be the same. And any action requiring code
> change must be requested in Bugzilla (so: if fixes are made in the
> French translation, volunteers will open an issue to integrate the
> fixes; same for any other actions).
>
> A translation never "starts": it is always open, and volunteers can ask
> for import from Pootle when necessary.
>
> I don't know how to put this process in the current version of the plan.
> What did you have in mind with the three translation phases? A full
> import at the end of each phase? We are not doing that and we won't so
> long as we use the current technology.
The 3 phases came from the reality in the past - at I remeber this way.
We made some last minutes changes into the build, even when it was after
the deadline.
So, IMHO we should count with this. That was the reason for the 3
different entries.
Of course this can be changed. It was just a first try to create a plan.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE PLANNING] New release planning template in the Wiki
Posted by Andrea Pescetti <pe...@apache.org>.
On 06/06/2014 Marcus (OOo) wrote:
> https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Planning+Template
> As promised some time ago I've now created a schedule plan for a new
> release.
This will surely be helpful. I made some changes, but I'm confused about
the three translation phases. For sure this part is not reflecting
reality, we don't have three translation phases. The process is as follows:
- We set a deadline for new translations to reach 100%
- We set a deadline for existing translations to be fixed in Pootle
- We set a deadline for updating/integrating dictionaries
- We currently don't set deadlines for the Release notes, but we could
The three deadlines can well be the same. And any action requiring code
change must be requested in Bugzilla (so: if fixes are made in the
French translation, volunteers will open an issue to integrate the
fixes; same for any other actions).
A translation never "starts": it is always open, and volunteers can ask
for import from Pootle when necessary.
I don't know how to put this process in the current version of the plan.
What did you have in mind with the three translation phases? A full
import at the end of each phase? We are not doing that and we won't so
long as we use the current technology.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org