> -----Original Message----- > From: Carl Trieloff [mailto:[email protected]] > > > But what's a dev "version"? The only time you can really have a > > meaningful "version" is when it's tagged and set aside. Dev > stuff is a > > moving target. Any given number assigned to "dev" today is not the > > same as tomorrow's. > > > > What does it mean to schedule a fix for "dev"? > > > > One late suggestion to the thread. after release update the > trunk to 0.7.
Right, but my point is that this week's 0.7 is not the same as next week's 0.7. So you still can't really identify what someone is working with just by saying 0.7, so what are we really buying with this scheme? > Then when we next release we make it 0.8. > > Thus moving forward all dev code will have odd numbers, and > releases will be even 0.6 0.8 0.10 / 1.0 etc. > > Carl. > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
