Re: Release Manager for 4.2.0?

[Matthias Seidel <ma...@hamburg.de>]

Hi Andrea,

Bouncing up your mail from march...

Am 27.03.2016 um 22:13 schrieb Andrea Pescetti:
> On 29/01/2016 Andrea Pescetti wrote:
>> For 4.2.0 we need a Release Manager. I would prefer NOT to be the
>> Release Manager for 4.2.0 since I'm finding that in this period I can
>> help more productively with tasks that do not require constant
>> interaction ...
>> I am surely available to have a significant role in the 4.2.0 release
>
> A few days after writing this, almost 2 months ago, sudden events left
> me incapacitated to make any significant contributions until very
> recently. I'm still unable to make long-term commitments.
>
> Anyway, there are some issues we need to get done as a team before
> appointing a release manager makes sense:
>
> 1) Enough code. Done. The merge of the recent gbuild work totally
> justifies a 4.2.0 release. Also, in 4.1.2 we only included a tiny
> fraction of the fixes that (at that time) were available on trunk. So
> here we are already OK, and we've been OK for months.
>
> 2) Localization. I got shell access to the Pootle server a few days
> ago. I'm still looking around, and if someone else want to join this
> is an important part. We need to have a solid process for updating
> translations (the full route: new strings in code -> Pootle -> back to
> code -> in localized builds) in place.

This is the part I would be interested to help!
Pootle synchronisation is essential for 4.2.0 and beyond.

Regards, Matthias

>
> 3) Buildbots and ASF-owned build machines. Buildbots are not essential
> for a release: 4.1.2 was built (like all previous releases in history)
> on non-ASF hardware; even if we build 4.2.0 on ASF-owned hardware, we
> can't use buildbots for it; we need to setup new systems. Those who
> read the infrastructure@ list can see the discussion I started there
> yesterday. Still, having buildbots helps QA and having ASF-owned build
> machines is an important investment for the project: at that point we
> will be able to make a release within days, not months. We should make
> as much progress as we can here. Again, if anybody can help, this is
> an important area.
>
> 4) There are several optimizations I have in mind, especially on
> reducing a bit our binary size on Linux (trust me, it is really a pain
> to commit all those binaries to SVN, or to any version control
> system). But they are not essential.
>
> I have just committed to the devtools/ area the scripts we (mainly
> Juergen) used to build the 4.1.2 release, with specs of the build
> machines. I've had them since last October, but I never committed
> them. They are a first step if we want to build our release binaries
> on ASF hardware: they contain build options and config.log to have
> some more information on the environment.
>
> My next priorities will be localization (especially, re-exporting the
> Italian translation to Pootle and re-importing it) and and a
> proof-of-concept VM for building releases on Linux (64 bit) based on
> the above scripts. There is plenty of room for other to jump in (Linux
> 32, Windows, Mac; or localization management) so please do!
>
> Regards,
>   Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>

Re: Release Manager for 4.2.0?

[Matthias Seidel <ma...@hamburg.de>]

Am 18.06.2017 um 16:47 schrieb Andrea Pescetti:
> Matthias Seidel wrote:
>> Bouncing up your mail from march...
>
> Not only from March, but from March 2016!

Wow, didn't even notice it...
But I must have thought it was important because I kept it in my
archive! ;-)

>
>> Am 27.03.2016 um 22:13 schrieb Andrea Pescetti:
>>> 2) Localization. I got shell access to the Pootle server a few days
>>> ago. I'm still looking around, and if someone else want to join this
>>> is an important part. We need to have a solid process for updating
>>> translations (the full route: new strings in code -> Pootle -> back to
>>> code -> in localized builds) in place.
>>
>> This is the part I would be interested to help!
>> Pootle synchronisation is essential for 4.2.0 and beyond.
>
> Good! So the first step would be that you try exporting a language
> (likely German in you case) from Pootle to SDF and check how it looks.
>
> While I assumed Pootle was aligned with 4.1.x (no strings are added
> within the 4.1.x series) Ariel did some work in early 2017 and found
> out that actually Pootle reflects some other, not perfectly clear,
> status of code.
>
> Anyway, the first action I suggest is:
>
> 1) Download German PO files from https://translate.apache.org/de/ (you
> will need to login; I've just given you permission to download the PO
> files in case you didn't have them)

Yes, that did work!
I will try the next steps...

And I just learned what the KeyID (lang="kid") is for, may be helpful!

Regards, Matthias

>
> 2) Convert the PO files to SDF; search "sdf" in
> https://wiki.openoffice.org for documentation
>
> 3) Compare the files you obtain with those at
> http://svn.apache.org/viewvc/openoffice/branches/AOO413/extras/l10n/source/de/
>
> (note: it's a huge text file, use some reliable editor)
>
> 4) You can also build the AOO414 branch -or trunk- with the new SDF if
> you want to have some fun.
>
> This is a first check to understand how stuff works and the
> translation status. Feel free to open a new dedicated discussion for
> follow-up if you need some more information. Note that I only know the
> high-level steps but I'm not familiar with details, so some
> documentation digging will still be needed.
>
> Regards,
>   Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>

Re: Release Manager for 4.2.0?

[Andrea Pescetti <pe...@apache.org>]

Matthias Seidel wrote:
> Bouncing up your mail from march...

Not only from March, but from March 2016!

> Am 27.03.2016 um 22:13 schrieb Andrea Pescetti:
>> 2) Localization. I got shell access to the Pootle server a few days
>> ago. I'm still looking around, and if someone else want to join this
>> is an important part. We need to have a solid process for updating
>> translations (the full route: new strings in code -> Pootle -> back to
>> code -> in localized builds) in place.
>
> This is the part I would be interested to help!
> Pootle synchronisation is essential for 4.2.0 and beyond.

Good! So the first step would be that you try exporting a language 
(likely German in you case) from Pootle to SDF and check how it looks.

While I assumed Pootle was aligned with 4.1.x (no strings are added 
within the 4.1.x series) Ariel did some work in early 2017 and found out 
that actually Pootle reflects some other, not perfectly clear, status of 
code.

Anyway, the first action I suggest is:

1) Download German PO files from https://translate.apache.org/de/ (you 
will need to login; I've just given you permission to download the PO 
files in case you didn't have them)

2) Convert the PO files to SDF; search "sdf" in 
https://wiki.openoffice.org for documentation

3) Compare the files you obtain with those at
http://svn.apache.org/viewvc/openoffice/branches/AOO413/extras/l10n/source/de/
(note: it's a huge text file, use some reliable editor)

4) You can also build the AOO414 branch -or trunk- with the new SDF if 
you want to have some fun.

This is a first check to understand how stuff works and the translation 
status. Feel free to open a new dedicated discussion for follow-up if 
you need some more information. Note that I only know the high-level 
steps but I'm not familiar with details, so some documentation digging 
will still be needed.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org