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 n
> On Aug 5, 2017, at 7:22 PM, Andrea Pescetti wrote:
>
> Jim Jagielski wrote:
>> My prep scripts are now on devtools/release-scripts.
>
> Thanks, one things less to redo next time!
>
>>> ## 3. How is the source code obtained?
>>> $ cd instsetoo_native/util
>>> $ dmake aoo_srcrelease
>> % pwd
>
Jim Jagielski wrote:
My prep scripts are now on devtools/release-scripts.
Thanks, one things less to redo next time!
## 3. How is the source code obtained?
$ cd instsetoo_native/util
$ dmake aoo_srcrelease
% pwd
/Users/jim/src/asf/code/aoo-414/main/instsetoo_native/util
% dmake aoo_srcreleas
Am 05.08.2017 um 20:46 schrieb Jim Jagielski:
> My prep scripts are now on devtools/release-scripts.
Since I am building for Windows in a VM I can use your hash-script on
Ubuntu. I only had to extend it to sign *.exe ;-)
Matthias
>> On Aug 5, 2017, at 1:13 PM, Andrea Pescetti wrote:
>>
>>
>> ##
My prep scripts are now on devtools/release-scripts.
> On Aug 5, 2017, at 1:13 PM, Andrea Pescetti wrote:
>
>
> ## 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
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 pas
