Re: The press release needs to be prepared in time

[Jörg Schmidt]

> From: Marcus [mailto:marcus.m...@wtnet.de] 

> Am 06.08.2017 um 10:20 schrieb Jörg Schmidt:
> > During the last releases there were problems with the 
> translation of the press release. Please let us create the 
> press release in time, so the time for translations remains.
> > 
> > note:
> > I myself will not create the press release, but I will help 
> with the German translation. (For this I need the English 
> original of the press release before the publication.)
> 
> I'm also not a native speaker, so why waiting? 

I have great difficulties with dealing with the English language and will not 
do so.

Also, my opinion is:
The draft content of the press release should come from the developers, because 
only these know the changes and extensions of the new program version from 
first hand.



greetings,
Jörg


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

Re: Save process and files turned to hashes

[Hagar Delest]

Le 31/07/2017 à 19:09, Patricia Shanahan a écrit :

It would be useful to have a survey of the configurations in which these 
problems happen. Are they associated with specific operating systems? More 
prevalent with network drives?

See: https://forum.openoffice.org/en/forum/viewtopic.php?f=6=17677#p81363
Mostly Windows users since it's the most common platform. But some other 
operating systems also.
Very few cases with network drives.

Hagar

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

Re: The press release needs to be prepared in time

[Marcus]

Am 06.08.2017 um 10:20 schrieb Jörg Schmidt:

During the last releases there were problems with the translation of the press 
release. Please let us create the press release in time, so the time for 
translations remains.

note:
I myself will not create the press release, but I will help with the German 
translation. (For this I need the English original of the press release before 
the publication.)


I'm also not a native speaker, so why waiting? You could start, e.g., 
with the structure and copy some text parts that could be the same. Then 
others can join and help you with the remaining parts. ;-)


Marcus


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

Re: Tips on uploading builds for 4.1.4-RC

[Jim Jagielski]

Thx. I've gone ahead and added this to


https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release

where it belongs.

> On Aug 5, 2017, at 1:13 PM, Andrea Pescetti  wrote:
> 
> I see that
> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
> does not contain many details on where/how to upload builds once we reach 
> (and it looks like we are almost there, thanks to everybody who helped!) the 
> Release Candidate stage.
> 
> Here are some notes based on past experiences (feel free to copy them to the 
> wiki as needed):
> 
> ## 1. Files and folders structure
> 
> See http://archive.apache.org/dist/openoffice/4.1.3/ for an example. Note in 
> particular that we have:
> source/ - more on this below
> binaries/ - they do include SDK, but they do NOT include kid
> 
> You'll probably want to assemble a quick script to move things into the right 
> place. Then please copy it to 
> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/ (I wrote a 
> similar script but can't find it right now).
> 
> Note: we can't change the structure since our download pages assume it is 
> identical for any 4.1.x release.
> 
> ## 2. Everything must come with hashes and signatures.
> 
> http://www.apache.org/legal/release-policy.html#release-signing
> 
> All files need:
> - md5 hash as filename.md5
> - sha256 hash as filename.sha256
> - A detached signature as filename.asc see 
> https://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig for 
> details
> 
> Who should make the signatures?
> - The Release Manager signs source
> - Other packages are signed by the person who provided them
> 
> Again, script should be copied to devtools/.
> 
> ## 3. How is the source code obtained?
> 
> It is *NOT* obtained via SVN export as one could imagine. You get it in a 
> source tree by running:
> $ cd instsetoo_native/util
> $ dmake aoo_srcrelease
> 
> I've modified it for 4.1.4 see 
> https://bz.apache.org/ooo/show_bug.cgi?id=127148 and also 
> https://bz.apache.org/ooo/show_bug.cgi?id=126605 so the output will not be 
> identical to 4.1.3 as some minor test files were not handled properly.
> 
> We still get the three formats (ZIP, gz, bz2). This will probably change 
> after 4.1.x as discussed a long time ago, but for 4.1.4 we should still use 
> the three of them.
> 
> ## 4. How are packages uploaded?
> 
> It's going to be a huge SVN commit to the dev area. My experience from a 
> couple years ago:
> - The SVN server has good reliability but it is slow, much slower than I 
> expected.
> - First, assemble all the tree in one location. In my case, I had setup a 
> space on fast-connected server where people uploaded their builds. This is 
> the best option, otherwise people will have to wait for each other and do a 
> full checkout (slow and huge).
> - Then structure files/folders as above
> - Then do the SVN commit. Due to speed issues, I recommend to script this and 
> upload one language at a time - unless the SVN server speed has increased 
> dramatically, but still you need one minute to script it so it's worth doing. 
> In my case, the SVN server was reliable but the gigantic SVN commit took 
> something like 20 hours from a machine that had no bandwidth problems; script 
> it and be safe (even if I expect that speed is better now).
> 
> Regards,
>  Andrea.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


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

Re: svn commit: r20825 - /dev/openoffice/4.1.4-RC1/binaries/kid/

[Andrea Pescetti]

On 06/08/2017 jim wrote:

Author: jim
Date: Sun Aug  6 00:24:52 2017
New Revision: 20825
Log:
Add in Language kid


Language "kid" is not released, see my "Tips on uploading builds" 
message. It is an internal fake "language" used to help translators 
identify strings.


The abbreviation "kid" stood for "Key ID" in the imagination of the 
developer who invented it, but it happens to be a valid ISO code for a 
real language called Koshin, so it's better not to distribute it.


It is, however, very valuable to have kid builds available somewhere, 
e.g., on a personal web space. They are especially useful when 
translators are working on the new strings - so not in the 4.1.x series, 
but for the 4.2.x releases.


Regards,
  Andrea.

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

The press release needs to be prepared in time

[Jörg Schmidt]

Hello,

During the last releases there were problems with the translation of the press 
release. Please let us create the press release in time, so the time for 
translations remains.


note:
I myself will not create the press release, but I will help with the German 
translation. (For this I need the English original of the press release before 
the publication.)


greetings,
Jörg



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