Marc Delisle schrieb:
Sebastian Mendel a écrit :
Marc Delisle schrieb:
Michal Čihař a écrit :
> Hi
>
> On Fri, 20 Jan 2006 08:15:12 -0500
> Marc Delisle <Marc.Delisle(a)cegepsherbrooke.qc.ca> wrote:
>
>> I think Sebastian's idea is to say that release 2.8.1 does not have
>> more features than 2.8.0, only bugfixes. Critical bugfixes can
>> still be named with -plX.
> Okay, this sounds reasonable for me. But maybe then we could abandon
> those -plX as it just complicates versioning scheme.
>
So it's time to clarify the branch names.
HEAD would contain the new features + obviously all the bug fixes.
RELEASE_2_8_0 would contain ... 2.8.0, what a surprise!
HEAD
- branch 2_8
- branch 2_8_0 // * 2006-01-23 *
release 2_8_0_0 // RC1
release 2_8_0_1 // RC2
release 2_8_0_2 // FINAL
release 2_8_0_3 // very quick release (security fix, pl1)
I find this
confusing. Are we talking only about CVS tags or also about
the naming of the downloadable files?
i was mainly talking about the cvs tags/branches
I prefer if users clearly see what they
download:
phpMyAdmin-2.8.0-rc1
phpMyAdmin-2.8.0
phpMyAdmin-2.8.0.1 (used to be 2.8.0-pl1)
the downloads don't need the last version numbers
2.8.0.0 can named as 2.8-RC1 or 2.8.0 RC1 as download file name
...
2.8.0.3 can named as 2.8-pl1 if you _really_ want this plx
2.8.1.0 can named as 2.8.1
2.8.1.1 can named as 2.8.1-pl1
i also often saw
2.7.9 as 2.8-RC1
2.7.9.1 as 2.8-RC2
2.8 as 2.8(-Final)
normally the last (fourth) number is the build number,