Re: [RFC][PATCH] NSE Version Numbering

[David Fifield <david () bamsoftware com>]

On Tue, Dec 14, 2010 at 09:31:06AM -0500, Patrick Donnelly wrote:
> Hi Djalal,
> On Tue, Dec 14, 2010 at 9:10 AM, Djalal Harouni <tixxdz () gmail com> wrote:
> > The version numbering is very simple e.g: 0.01 (Lua number) this value
> > will be incremented if there are some new NSE features that will have
> > a direct impact on NSE scripts/libraries and will *modify* their
> > behaviour, or a change on the NSE *core* functionalities, anything
> > related to the NSE core. As an example modifying/adding nse_*.cc
> > interfaces must be documented in the luadoc files:
> > file nmap.luadoc:
>
> I've given this some thought and my take is that version numbers
> should probably be the revision number in the repository. So long as
> Nmap remains on subversion, this makes sense and is automatic. It
> should be trivial to make adding (updating) this field automatic in
> the build process.

I was just thinking that this won't work when releases are built from
branches. Numbers are global across the repository so the number in, for
example, /nmap-releases/5.51 could be ahead of that in trunk even though
it might not have the same NSE updates as trunk.

David Fifield
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/