[tasklist] tasklist module version numbers

Tor Norbye <[email protected]>
Newsgroups gmane.comp.java.netbeans.modules.tasklist.devel
Organization Sun Microsystems, Inc
Message-ID <1047659987.3861.1581.camel@proto>
Hi,
you may have seen Jesse's post on nbdev recently about
changing version numbers for modules.

Apparently, the trunk version must always be more recent than
the release35 branch version.

With our current naming scheme that won't work, since we use
x.y.z for both, so if there's a bug fix in the branch, rev'ing
it may cause the version number to match a trunk version.

Here's how we can solve that:
in the trunk, use only two integers for the version:
x.y
and then bug fixes and maintainance updates use x.y.z.

Since we're at 0.9.x now I'd rather not go to "0.10", since that 
will look more like "0.1" than "0.9+0.1". So I propose we shortly
declare "1.0" on all the modules (except buglist and compiler, since I
don't think they're feature complete yet, although speak up Tim and
Andrew if you disagree).

So the modules in the release35 branch will be numbered 1.0,
and then 1.0.x as additional fixes are applied.

All the trunk modules will be version 1.1 (not 1.1.x). So in not
too many revs, the core module in the trunk might for example be
at version "1.24". If at that point a split into a NetBeans 4.0
branch occurs, the branch versions would be "1.24.x".

Does this make sense? Unless I hear objections I will make
these changes soon. I will let Tim control the compiler version
number and Andrew control the buglist version number so you can
decide when it should reach 1.0.

-- Tor
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.