Hi all, See the previous message in this thread.
There's one little problem left: Currently, everything in B_Release is identical to HEAD (at least as it was yesterday afternoon). Thus, the B_Release branch probably contains some unpublishable documents. I'm checking my own manuals to see if the latest committed version is publishable, and I would like to ask all of you to do the same. Most of us don't maintain many documents, so I hope it's not too much work. If you discover a document that is not publishable in its latest committed state, then: - If it's easy to fix and you have the time, then I suggest you do that. Then commit it to HEAD *and* to the B_Release branch. (And tag it, at the very least in MAIN, if you want to do any merging later, instead of just overwriting the B_Release copy every time.) - If not, check which committed revision is the most recent that's publishable (e.g. via http://firebird.cvs.sourceforge.net/viewvc/firebird/manual/). Then we can move the branch tag for that document. Cheers, Paul Vinkenoog ------------------------------------------------------------------------------ 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks & Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
