Follow-up Comment #5, task #2171 (project savane):
> A new MAJOR version marks a significant change in the code. The upgrade
from
> one major version to another may be rather hard, may require new
prerequisite
> technologies, full data dump, reload and reindexing, as well as other
major
> configuration adapatations, possibly with an important manual
intervention.
>
> A new MINOR version indicates new functionality and bugfixes. The upgrade
from
> one minor version to another may be laborious but is relatively painless,
in
> that some table changes and data manipulations may be necessary but they
are
> somewhat smaller in nature, easier to grasp, and possibly done by an
automated
> script.
>
> A new PATCH version means that only bugs are fixed, without adding any
> substantially new functionality. That is, the only new functionality that
is
> added is that of a bug fix nature. The upgrade from one patch level to
another
> is usually straightforward."
A bit long! What matters with release number is that people get an idea of
how things evolves. But this is probably overkill, dont you think?
But I agree with your definitions apart the PATCH one, since it really looks
like a release. While the idea of making release containing only trivial
bugfixes is not a bad one, we currently do not make such release. The +1 is
more a repackaging with a little change actually replacing the release of the
same main number.
> Last, but not least, I hope that we'll never need to release a Savane
version
> of 1.1(.|+)1, so this would become a non-issue. ;-)
Well, I think we'll soon test a 1.0.8+1 -> bug #2839
_______________________________________________________
Reply to this item at:
<http://gna.org/task/?func=detailitem&item_id=2171>
_______________________________________________
Message posté via/par Gna!
http://gna.org/
_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev
