openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrea Pescetti <>
Subject Re: procedure for going from RC to release
Date Sun, 03 Apr 2016 15:49:15 GMT
On 03/04/2016 Marcus wrote:
> Am 04/03/2016 03:34 PM, schrieb Carl Marcum:
>> Are the artifacts and signatures copied to new names or recreated and signed?

They are moved, using svn move.

> If it's for the NetBeans plugin you can look at the name structure above
> for the AOO files. Maybe it's possible to adopt it completely or do some
> changes where it makes sense.

For the "real" OpenOffice release there is nothing to discuss. Files are 
uploaded to the staging area and from there to dist.

For this "extra" Netbeans plugin release (in the meantime I have taken a 
look at the sources and I found it is much more complex than what I 
thought, so it's reasonable to attempt a proper release) I suggest that 
we add one source-only file to the existing folders.

Specifically (this is extremely important so please ask again for any 
doubts, or you will break a lot of technical assumptions):

1) You upload the RC (one source file, with hashes/signatures) in a new 
subdirectory of (say, 
); and you call the file something like netbeans-plugin-r1800000.tar.gz, 
reflecting the SVN revision it comes from.

2) After a successful vote, the one file you placed there (accompanied 
by its hashes/signatures) is moved (using svn move) to dist. The target 
directory to use is this one: ; 
please do not create anything else, the plugin sources will live in the 
source directory of the matching (or closest in time) OpenOffice release.

As discussed, binaries for the Netbeans plugin are not released on the 
ASF infrastructure, so after approval you are free to build and sign 
them according to the rules needed on; and no copy of them 
will be preserved on dist.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message