søn, 11 05 2008 kl. 23:40 +0200, skrev Thomas Weber: > I'm about to update the forge packages in Debian, but noted something > surprising. The control package had no code changes in 2008, but its > version went from 1.0.4 to 1.0.6 during the releases. > > Is this intentional?
I don't remember the details of this package, but sometimes we have been forced to bump version numbers even if no code changes have happened. This is related to the scripts we use to make the releases. As an example, it seems that my version of 'svn2cl' doesn't generate the exact same output as Davids version does (at least that's how I remember things). So, if David released version X of a package I might need to release version X+1 later on even if no code has been changed -- simply because the ChangeLog has changed. So, things aren't perfect right now. At some point in the future it would be nice if we didn't have to make releases of Octave-Forge. It would be better if the individual package maintainers released their own packages independently. Then we wouldn't see the kind of 'random' version bumbs that you've noticed. Søren P.S. I don't remember all the details involved here (I have a terrible memory), so things might not be 100% correct... ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
