----- Original Message ----- From: "Joost Andrae" <[email protected]> To: <[email protected]> Sent: Friday, June 26, 2009 04:34 Subject: Re: [discuss] Re: 3.1 vs. 3.2
> DEV300_m50 is a developer build, not a release build. > > ______ ______ > |OOO310| |OOO320| > |______| |______| > | | > ----DEV300------------DEV300-----------DEV300---- > > Release codelines like OOO310 are branched-off the TRUNK/HEAD of SVN > repository which is called DEV300 for a moment. Release branches are > created to stabilize a release and to allow further development on the > "unstable" TRUNK/HEAD. This TRUNK/HEAD (DEV300) may be renamed (to eg. > DEV400) when the next major version is planned. This helps. Thanks. It made it a little cryptic as to where to find them. I've never been afraid of beta versions. Or pre-betas, alphas, pre-releases, and, as it's termed here, developer's builds. I've learned that every OOo build is pretty solid as it is and is more than adequate for me in any version. I did, however, get lost slightly after the 3.1 release build arrived as to where forthcoming versions were that had been talked about. The only thing (I mentioned this before) that eludes me is the cross-platform nature of open source programs makes it seem like there is a standard "help file" format and I'm not sure how to read this help file outside of the program. Example a .chm or .hlp can be opened using hh.exe, winhelp.exe or winhlp32.exe or in many instances, by double clicking on the help file. OOo is different. How can it be done? Someday I will be able to purchase a printer and run off the pages I desire. Until then a reference on demand would be useful. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
