Hello Keith, On Sat, Jan 02, 2021 at 12:55:07PM -0500, Keith N. McKenna wrote:
> On 1/2/2021 4:48 AM, Arrigo Marchiori wrote: > > Hello Keith, > > > > On Fri, Jan 01, 2021 at 07:30:17PM -0500, Keith N. McKenna wrote: > > > >> On 1/1/2021 10:06 AM, Arrigo Marchiori wrote: > >>> Dear dev@ and doc@ lists, > >>> > >>> this message is to inform you that I am (slowly) beginning to put my > >>> proposal in action. > >>> > >>> There is a thread on dev@ that is about archiving old web pages, that > >>> is currently on hold for the holiday time. I will _not_ wait for that > >>> thread to reach a conclusion, because I honestly believe that > >>> archiving build instructions for individual releases does not really > >>> fit in the purpose of that thread. > >>> > >>> If anyone thinks that I am wrong, and that I should instead wait until > >>> that thread has come to a conclusion, then please just tell me, and I > >>> will stop and revert any changes. I am just trying not to lose time, > >>> in the interest of the project. > >>> > >>> I take the occasion to wish a happy 2021 to everybody! > >>> > >> rigio; > >> > >> Irregardless of the archiving thread, I am having a difficult time > >> seeing the need for per build instructions.I see nothing in the per > >> revision instructions that is not covered in the generic instructions or > >> would be better placed in the OS specific instructions. > >> > >> Please understand that I look at this purely from a documentation > >> standpoint as I do not build. From my reading the Build Guides > >> instructions appear generic enough and link to more specific instruction > >> for for different operating systems. Please help me understand what I > >> may be missing. > > > > The problem, IMHO, is exactly that they are generic. Because > > everything changes, like the linked tools (dmake, EPM), the build > > system itself may evolve, and even the source repositories have > > changed, it becomes more and more difficult to reproduce the _exact_ > > build of a past release. > > > > I expect such builds to become useful for hunting regression bugs. > > > Hi rigio; > I understand what you are saying,but those detailed instructions are > already in the per OS section and seem to me to be superfluous in the > basic setup section. Also there is already a procedure defined in > Section 9 on how to build older versions specifically aimed at > regression testing.We never release from trunk. It is only used by the > build bots for our nightly and weekly builds. We *only* Release from > the current branch. > > I hope this makes my position more understandable. Even though I do not > currently build the software, I could setup a build environment and > build without the per branch instructions Yes, thank you for further explaining your point. The reason behind my proposal and edits is simple: I could not find the information _easily_ enough. Now I think I can use what you wrote in this and in your previous message to better elaborate the topic of building older versions, and then leave it all on a single page. As I am poking into the other pages to make other edits, I found more than one link to the build scripts, that I could not see when I first started trying to build OpenOffice. I thought that Mechtilde's "AOO Bauen" page [1] was the only one mentioning the build scripts it and now I know I was wrong. This makes my work overall less urgent than I expected, but I am still commited to do it because I think that the build documentation is still worth a little re-organization. As an example: the release builds are IMHO the most interesting ones, and I am going to rerrange the chapters into the step-by-step building guide to list them before other platforms and experimental setups. After all, wiki edits can always be reverted; so if the majority of people here strongly disagrees with me, I will just end up having gained some experience on MediaWiki. ;-) References: 1: https://wiki.openoffice.org/wiki/User:Mechtilde/AOOBauen -- Arrigo http://rigo.altervista.org --------------------------------------------------------------------- To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org For additional commands, e-mail: doc-h...@openoffice.apache.org
