On Thu, Jun 26, 2003 at 01:37:11PM +0200, Dirk Meyer wrote:
I hope we can release 1.3.2-pre5 this weekend. Last time I asked Rob
about it, he only wanted to make small changes in the runtime. Based
in that, we should code-freeze Freevo for now. Only bugfixes and
cleanups are allowed till pre5 is out. I don't want to break it before
the release. Rob: we should sync us in IRC about release time.
I'm thinking that our version numbering is very misleading. A lot of people are running the last "stable" version (1.3.1) instead of the preX versions because the 'pre' implies that it's unstable, however, I would argue that the 1.3.1 releases and older are pretty unstable.
Perhaps we should move to something like this:
1.3.1.1, 1.3.1.2, etc.
or
just make the next release 1.4, and make point releases for snapshots
during it.
Hmm, I think that 4 version numbers is a bit much (1.3.1.1). I would much rather see us increment versions more often, like release 1.3.2 asap and have the next release either 1.3.3-rc1 (and no more than 1 or 2 rc's MAX) and move to 1.3.4 or 1.4.0 quickly.
major_version.minor_version.patch_level is a pretty good way to go and you are right, we are making significant changes so perhaps we should bump up the minor version more often.
my 2 cents -Rob
------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
