On 7/27/06, Travis Oliphant <[EMAIL PROTECTED]> wrote: [snip] > I don't really like having the trunk use a 'lower' version number than > the releases but I'm not sure what to do. The problem seems to stem > from wanting to have the version number sort somewhat reasonably when > the development number is tacked on. > Don't fix it if it ain't broken. Applications that need sortable version numbers can work out their own convention. For example, 1.0.0.<svn rev>, 1.0.0.final, 1.0.1.<svn rev>. Numpy was following a consistent and convenient rule for a long time, changing that now will only lead to confusion.
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion
