Hi Norman, >I've been reading through the Firebird 3 (Alpha) Release Notes this >morning and I'm seeing a few changes over and above previous versions. > >I am suggesting that we start afresh (!) from this release with our >documents. I know this might be extra work and we all suffer from a lack >of time as it is, but my docs at least, already have a number of "this >only applies in Firebird 2.x" or similar and I'm not sure I can cope >with adding in extra bits that are relevant to Firebird 3.x as well. I >think it gets a little messy. > >I would suggest that we copy the existing docs to a new folder, >possibly, and file specifically for version 3.x and edit out the bits >that no longer apply to Firebird 3.
Most of our docs are not going to be worked on in the foreseeable future. So copying the bulk of our docs when only a few of them will be updated doesn't seem like a good idea to me (but maybe I got your intention wrong). But I fully support starting afresh with the actively maintained docs. How about using branches for this? Cheers, Paul Vinkenoog PS: I'm on a two-week vacation, with Internet access on my current location. Next week (9-16 August) probably also, but that's not 100% certain yet. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Firebird-docs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/firebird-docs
