Stable, Final, Release candidate or what? Topic is solved

Here you can contact the editors of our Extensions site, as well as access infomation relating to this site.

Moderators: tydust, LorenzoG, timothy.stiffler

Forum rules
Forum Rules
READ ME <-- please read before posting, this means YOU.
Post Reply
TomasA

Stable, Final, Release candidate or what?

Post by TomasA » Sat May 13, 2006 11:05 am

I'm a little bit confused about what’s final, release candidate, beta version and so on. After looking through the extensions, as example Anjel at
http://extensions.joomla.org/component/ ... Itemid,35/ It seems to be a stable version, but looking further I found that it is called ANJEL 0.6.1 Final.

I’m new to Joomla community and has planes to migrate my sites to Joomla. If so, I’m not interested in implement non stable extensions in my productive sites. Compare with an other option of CMS – Typo3 – where they clearly announce if the extensions are stable or not.
Is it not possible to state roles in Joomla extension community concerning versions of stability or not in the extensions?

/ Tomas

User avatar
mjaz
Joomla! Intern
Joomla! Intern
Posts: 63
Joined: Thu Nov 10, 2005 10:08 am
Contact:

Re: Stable, Final, Release candidate or what?

Post by mjaz » Thu Jun 08, 2006 7:25 am

I agree. It should either be more obvious if an extension isn't stable, or there should be a rule about against submitting unstable extensions. I think I prefer the latter, as it will make the directory more useable and less like the projects list at the forge.
Joomlatools Team Member - DOCman Lead Developer
http://www.joomlatools.org
Read the blog!
http://blog.joomlatools.org

TomasA

Re: Stable, Final, Release candidate or what?

Post by TomasA » Thu Jun 08, 2006 7:46 am

I have always belived that the first stable official version of any software are v1.0.0

If you look at the Version Convention i Joomla Developer Roadmap you can read as follows:

Version Convention
Joomla! release versioning follows a numerical convention comprised of three numbers: Major, Minor and Maintenance.  The version is presented in the major.minor[.maintenance] format.

Major Release Number (X.1.1)
An increment of the major number generally indicates a major rework or rewrite of the code base.
May be completely incompatible with prior major releases.

Minor Release Number (1.X.1)
An increment of the minor number usually indicates a significant change to functionality or architecture.
Moderate to high level of backward compatibility with previous minor increments.

Maintenance Release Number (1.1.X)
An increment of the maintenance number usually indicates bug fixing within the minor release and possibly small enhancements and limited new features.
Fully backward compatible with previous maintenance increments


I really would like to hear any software/extension developer explain their point of view of why calling a minor release number Final.

/ Tomas

User avatar
ivo.apostolov
Joomla! Intern
Joomla! Intern
Posts: 73
Joined: Thu Aug 25, 2005 2:33 pm
Location: Sofia
Contact:

Re: Stable, Final, Release candidate or what?

Post by ivo.apostolov » Sat Jun 10, 2006 9:12 am

I think, extension owners MUST be forced to write the status in the version field.
Ivo Apostolov
Joom!Fish Team • Translation Workgroup • Joomla! Bulgaria
http://www.joomfish.nethttp://ivo.unwe.net - Personal Blog

User avatar
mjaz
Joomla! Intern
Joomla! Intern
Posts: 63
Joined: Thu Nov 10, 2005 10:08 am
Contact:

Re: Stable, Final, Release candidate or what?

Post by mjaz » Sat Jun 10, 2006 2:05 pm

It could be a simple drop-down list. Extensions that are stable could go to the top of the list. That could be an extra incentive for 3PD's to finish their extension.  :)
Joomlatools Team Member - DOCman Lead Developer
http://www.joomlatools.org
Read the blog!
http://blog.joomlatools.org


Post Reply