Re: procedure for going from RC to release

Am 04/03/2016 10:10 PM, schrieb Carl Marcum: On 04/03/2016 03:42 PM, Andrea Pescetti wrote: Carl Marcum wrote: I was looking at how some other projects handled "extras" things like this. Other projects designed their trees in a different way. I found Maven uses sub-folders under

Re: procedure for going from RC to release

Am 04/03/2016 09:42 PM, schrieb Andrea Pescetti: Carl Marcum wrote: I was looking at how some other projects handled "extras" things like this. Other projects designed their trees in a different way. I found Maven uses sub-folders under release/maven for plugins, plugin-tools, etc, that

Re: procedure for going from RC to release

On 04/03/2016 04:25 PM, Andrea Pescetti wrote: Carl Marcum wrote: I hope you don't take my suggestion for disagreement. Of course not. Let's simply find together the right way to publish this source package in the tree. As I wrote, I am OK with adding devtools/ provided this doesn't break

Re: procedure for going from RC to release

Carl Marcum wrote: I hope you don't take my suggestion for disagreement. Of course not. Let's simply find together the right way to publish this source package in the tree. As I wrote, I am OK with adding devtools/ provided this doesn't break the JS generation for download page. I see no

Re: procedure for going from RC to release

On 04/03/2016 03:42 PM, Andrea Pescetti wrote: Carl Marcum wrote: I was looking at how some other projects handled "extras" things like this. Other projects designed their trees in a different way. I found Maven uses sub-folders under release/maven for plugins, plugin-tools, etc, that don't

Re: procedure for going from RC to release

Carl Marcum wrote: I was looking at how some other projects handled "extras" things like this. Other projects designed their trees in a different way. I found Maven uses sub-folders under release/maven for plugins, plugin-tools, etc, that don't go into their main release folder. [1]. Well,

Re: procedure for going from RC to release

On 04/03/2016 11:49 AM, Andrea Pescetti wrote: 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

Using the @ApacheOO Twitter Account

The @ApacheOO Twitter account is operated by an individual (the only option for free accounts). A Member of the Project Management Committee operates the account. However, everyone can use it and use its Twitter ID. First, subscribing to @ApacheOO on Twitter will provide notices about

Re: [HELP NEEDED] old Solaris related build issues

Am 04/03/2016 06:56 PM, schrieb Απόστολος Συρόπουλος: We have a number of old Solaris related build issues that could use some testing. https://bz.apache.org/ooo/show_bug.cgi?id=125361 https://bz.apache.org/ooo/show_bug.cgi?id=125362 https://bz.apache.org/ooo/show_bug.cgi?id=125364

RE: [HELP NEEDED] old Solaris related build issues

> > We have a number of old Solaris related build issues that > > could use some testing. > > > > https://bz.apache.org/ooo/show_bug.cgi?id=125361 > > https://bz.apache.org/ooo/show_bug.cgi?id=125362 > > https://bz.apache.org/ooo/show_bug.cgi?id=125364 > >

Re: Let's fix the Windows build bots

On Mon, Mar 28, 2016 at 10:53 PM, Andrea Pescetti wrote: > On 01/02/2016 j.nitschke wrote: >> >> But a global haltOnFailure would stop the build at 'svn info' step. >> About the 'svn info' step, this one stopped working ... > > > And we are back here, it seems. With the HTTPS

Re: procedure for going from RC to release

On 04/03/2016 11:41 AM, Dennis E. Hamilton wrote: The RC artifact that is approved as a release is the artifact that is released. If you check the last RC for AOO 4.1.2 at you'll see that the folder has the RC name, tied to the source tree.

Re: Let's fix the Windows build bots

On Mon, 28 Mar 2016 22:53:43 +0200 Andrea Pescetti wrote: > And we are back here, it seems. With the HTTPS fixes now in place, all > the Linux and FreeBSD buildbots completed their build successfully, > while the Windows one ran build --all but then suddenly stopped almost > at the end, after

Re: procedure for going from RC to release

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

RE: procedure for going from RC to release

The RC artifact that is approved as a release is the artifact that is released. If you check the last RC for AOO 4.1.2 at you'll see that the folder has the RC name, tied to the source tree. In that folder, the files are all identified

Re: procedure for going from RC to release

Am 04/03/2016 03:34 PM, schrieb Carl Marcum: I'm looking for the procedure for how the approved RC files are released. are you looking for the general release process for AOO? Or for the Netbeans plugin you are creating? Are the artifacts and signatures copied to new names or recreated and

procedure for going from RC to release

I'm looking for the procedure for how the approved RC files are released. Are the artifacts and signatures copied to new names or recreated and signed? I know where they go but not how the names are changed. Thanks, Carl -