Dmitry wrote: > Unstable or in-progress versions can be left on your side, no problems. > But I was surprised to know that the version which is published on the > official site was not committed. This should never happen!
100% agreed. >> With the documentation, there's no overall release cycle. Every manual is >> published if and when it is ready. Creating tags for every new release of >> every single document is crazy. Creating branches for every document that's >> being worked on: same. I've thought about doing it for some of my own >> documents once or twice, but in the end I decided not to. Even if I would do >> it consistently, I doubt if all the others would. And if they would, we'd >> soon have a forest of tags and branches in the repository. >> >> Still, we can give it a try if the others feel like it. Formally, it is the >> right approach. > We can start with a simple solution. Just create a single "release" > branch which gets modified the every time we publish something on the > site. The HEAD branch must keep at least the same version as the > "release" one. It may also have newer (immature) versions committed, but > it is up to the author. Hmmm... so any "dirty" versions are committed to HEAD (or stay on Helen's computer), and as soon as something can be published, it's committed to the release branch. Simple and effective! Why, you don't even need tags with this approach - although you can use them if you want to. Now why didn't *I* think of this? :-) I'm all for it. It only requires some extra attention to our local copies; we have to know whether we're on a branch or not while working on the sources. But even that is simple: all the editing work is done in HEAD. Paul Vinkenoog ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
