Jarifa version numbering
1 view
Skip to first unread message
ChristianB
Nov 30, 2008, 4:50:21 AM11/30/08
to Jarifa
Today I wanted to add some task tickets and milestones to trac but
then I realized that Jarifa has no visible version number. The git
revision numbers are not suitable for this so we kind of need a way to
control different versions. I propose the following changes:
Reorganize the repository so that it contains a trunk, tags and
workspaces directory. Define a definition for major and minor version
numbers (e.g. 0.1 means beta, 1.0 means first full featured release).
Major version will increase when new features are added and minor
version increases when bugs are fixed for this particular major
version. This is similar to the Wordpress version numbering (they have
two minor numbers) which is IMHO a good way for small PHP only
projects.
According to the git-tree, Jarifa is currently in the 1.0-rc2 stage.
But there are no tags. Now we have to define what should be done to
release the 1.0 version. I would like to implement the installer in
the 1.0 version also.
Regards
Christian
then I realized that Jarifa has no visible version number. The git
revision numbers are not suitable for this so we kind of need a way to
control different versions. I propose the following changes:
Reorganize the repository so that it contains a trunk, tags and
workspaces directory. Define a definition for major and minor version
numbers (e.g. 0.1 means beta, 1.0 means first full featured release).
Major version will increase when new features are added and minor
version increases when bugs are fixed for this particular major
version. This is similar to the Wordpress version numbering (they have
two minor numbers) which is IMHO a good way for small PHP only
projects.
According to the git-tree, Jarifa is currently in the 1.0-rc2 stage.
But there are no tags. Now we have to define what should be done to
release the 1.0 version. I would like to implement the installer in
the 1.0 version also.
Regards
Christian
ChristianB
Nov 30, 2008, 8:19:05 AM11/30/08
to Jarifa
> Reorganize the repository so that it contains a trunk, tags and workspaces directory.
I just read a tutorial about tagging and branching with git so please
ignore this sentence.
Daniel Lombraña González
Dec 1, 2008, 3:50:39 AM12/1/08
to jar...@googlegroups.com
Perfect, Git is really awesome ;)
--
··························································································································································
PhD Candidate
Cátedra Ceta-Ciemat de la Universidad de Extremadura
http://gea.unex.es/catedra-ceta-ciemat/
Universidad de Extremadura
··························································································································································
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··························································································································································
2008/11/30 ChristianB <open.sou...@googlemail.com>
I just read a tutorial about tagging and branching with git so please
> Reorganize the repository so that it contains a trunk, tags and workspaces directory.
ignore this sentence.
--
··························································································································································
PhD Candidate
Cátedra Ceta-Ciemat de la Universidad de Extremadura
http://gea.unex.es/catedra-ceta-ciemat/
Universidad de Extremadura
··························································································································································
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··························································································································································
Reply all
Reply to author
Forward
0 new messages