2) How should we name our bracnhes? - Is there a nomenclature to stick to for new branches? - Is it OK to branch from the current working copy by something like: cvs tag -b FOSSFA-0.1
Elpidio Latorilla wrote:
I would suggest you name it FOSSFA_0_1
I would strongly suggest an already widely used naming convention. That would mean something like: fossfa-0.1
The why explanation could be taken from various sources, but lets try Eric Raymond's "Software Release Practice HOWTO":
"3. Good project- and archive- naming practice:
As the load on maintainers of archives increases, there is an increasing
trend for submissions to be processed partly or wholly by programs (rather than entirely by a human). *This makes it more important for project and archive-file names to fit regular patterns that computer
programs can parse and understand*
3.1. Use GNU-style names with a stem and major.minor.patch numbering.
It's helpful to everybody if your archive files all have GNU-like names, i.e., *all-lower-case alphanumeric stem prefix, followed by a dash, followed by a version number, extension, and other suffixes*.
Let's suppose you have a project you call `foobar' at version 1, release 2, level 3. If it's got just one archive part (presumably the sources), here's what its names should look: *foobar-1.2.3.tar.gz*
Please don't use these:
foobar123.tar.gz - This looks to many programs like an archive for a project called`foobar123' with no version number.
foobar1.2.3.tar.gz - This looks to many programs like an archive for a project called `foobar1' at version 2.3.
foobar-v1.2.3.tar.gz - Many programs think this goes with a project called `foobar-v1'.
foo_bar-1.2.3.tar.gz - The *underscore is hard* for people to speak, type, and remember.
FooBar-1.2.3.tar.gz - Unless you like looking like a marketing weenie. This is also hard for people to speak, type, and remember.
Please don't use names like `foobar-ELF-1.2.3.tar.gz', because programs have a hard time telling type infixes (like `-ELF') from the stem.
A good general form of name has these parts in order: 1. project prefix 2. dash 3. version number 4. dot 5. "src" or "bin" (optional) 6. dot or dash (dot preferred) 7. binary type and options (optional) 8. archiving and compression extensions."
Perhaps we would be better if we could keep it with what are already pretty standardized practices.
A final word: why name it fossfa?
Is this branch something paid by FOSSFA? Is it officially sponsored by FOSSFA? Should the Care2x project bother with it?
It would be more meaningful to name it after that branch initiator and main developer, in this case Kurt Brauchli (kurt-0.1).
Better yet, as Kurt said that it will include country (regional) specific code, we could prefix it with the ISO 2 letter code of the country for which it is being adapted.
In that case, while developing Denmark specific code, Kurt would add to the [dkkurt-0.1] CVS branch, and if he ever started to develop USA specific code he would add to a CVS branch named [uskurt-0.1].
That way we would know at a glance which of the CVS branches were country specific. Also, for each given country we could easily see who was the developer (or group name of developers) in charge for that branch.
That way we could keep it simple, both human an machine (software) readable, and still not impose unnecessary constraints to future development.
Best Regards,
J. Antas
P.S. - The Eric Raymond's "Software Release Practice HOWTO" manual, and many other manuals, like "Free Software Project Management HOWTO", are freely available in various formats, including .pdf from the HOWTO and the Manuals sections of the The Linux Documentation Project site at: http://www.tldp.org/
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ Care2002-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/care2002-developers
