Hi Lester! >>> 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.
> This might ACTUALLY be a situation where hg ( or git is you must ) can be made > to work ... I'm sure they could, but, under(wo)manned as we are, I wouldn't like to invest time in unnecessary changes. CVS is far from ideal, but it's more than good enough for our modest workflow. And Dmitry's proposal is simple and effective. If there are no objections, I will create a B_Release branch next week. Cheers, Paul Vinkenoog ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
