Re: procedure for going from RC to release

On 04/03/2016 06:17 PM, Marcus wrote: 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 fo

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 release/mav

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 don'

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 th

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 oth

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 stru

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: 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 possib

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 by

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