On 8/21/08, Ken Kuhlman <[EMAIL PROTECTED]> wrote:
>
>  On Thu, Aug 21, 2008 at 7:28 AM, Christopher Arndt <[EMAIL PROTECTED]> wrote:
>  >
>  > Christoph Zwerschke schrieb:
>  >> Updating the CHANGELOG is already on my todo list, since a couple of
>  >> other things have been fixed so we should think about making another
>  >> bugfix release soon. (Maybe not 1.0.6 but 1.0.5.1, because the fixes are
>  >> not so large and we will run out of version numbers too quickly?).
>  >
>  > Maybe we should have a definition of what constitutes a point release
>  > (1.0.*.x) and what a full 1.0.x release? Anyway, I don't see why we
>  > should stop at 1.0.9. 1.0.10 seems a perfectly valid version number to
>  > me (not that I *want* to maintain TG 1.0.x for that long).
>  >
>  > Florent, do you have any opinion on this (as the official 1.x release
>  > manager)?

I don't want to go for sub-numbers for marketing reasons. Since we
don't want to do a lot of enhancements I think we can afford to
continue only on 3 digits with 1.0.X, where X could run as high as we
need.

>  >
>  > On a related matter, why does the release.py file in the 1.1 branch
>  > state "1.5" as the version number and the 1.5 branch has "1.6"? I'm
>  > confused.

Ken already answered. 1.5 version was because I was preparing to
change the 1.1 branch into an 1.5 branch for marketing reasons and
because 1.1 had do many good things. Then Ken popped up and proposed
to have CP3 support. But since CP3 support could not be introduced in
one jump (testing framework wise) we decided he would create a 1.5
branch for the work.

We'll rollback this version number from 1.5 to 1.1 in the 1.1 branch then.

Florent.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to