> Am 16.09.2024 um 12:39 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at>:
> 
> Hi P.O.,
> 
> On 15.09.2024 18:11, P.O. Jonsson wrote:
>> From the non-response to this request I take it that there is no interest in 
>> a release procedure and even less a future release? If there is no interest 
>> there is no point in me trying to come up with a better release procedure 
>> than the last time :-(
> 
> well, I can understand your frustration in that no one communicates, let 
> alone gives any feedback.
> 
> OTOH you may be a little bit too impatient :) given that people may be on 
> vacation (like myself) or being consumed by other non-ooRexx tasks to an 
> extent that hinders them to download and check out the results of your hard 
> work, which I think is *great*, seriously!
> 

Well, I had set up a staged folder on sourceforge for the test, and I had to 
delete it today since it would otherwise become visible to the public after 3 
days, hence the frustration, no-one had looked at it before it had to be 
deleted :-(.

> It is nice to now see the production date and revision of the pdf files and 
> also when the last change (together with the revision) the individual pdf 
> books took place, so thank you very much for these improvements, kudos!
> 

I am not responsible for those amendments, I think that is Gil’s work (and 
brilliant it is), all I have done is to make sure that the documentation build 
job on Jenkins can be switched to be rebuilt completely and automatically at 
the time of a release, that MUST be ready before we start to build the 
artifacts. But I need to know if the layout is ok for a release or if I need to 
do some further modifications. For most documents it will look like

Edition Date.Of.The.Release (last revised on 2024-09-08 with r12905)

But for oodialog et al this is not the case. Also for some smaller docs like 
oosqlite.pdf the layout is different. Maybe not a big deal. For all books we 
need to revise the list of contributors in due time before a release as well.

> Looking for your work to be merged to trunk!

It is already in trunk

> 
> Best regards
> 
> ---rony
> 
> 
> 
> 
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to