As of September 1st, I accepted a new job, and I'm currently still in the
aftermath off finishing my home-improvement duties. On top of that, something
has gone terribly wrong with moving my ADSL line, so I'm effectively still
without an internet connection at home. Last year I volunteered as release
manager, and with some recent talk of the desirability of another possible
release sometime soon, I thought, I'd throw in my thoughts. With my move
planned, I already knew that a release before the end of the year might be out
of the question. However, a Christmas release, like we did last year, would
most likely be possible from my perspective.
Given that we have an OSG branch that has undergone significant development
this year, and a PLIB branch, with little or no development, I would strongly
urge that the main release would be OSG based. However, having said that, I
would not object against a small maintenance release of the PLIB branch. The
latter would be just a wrap-up of the current source and data directories, but
without extensive bug fixing.
As for a version number scheme, I don't think this issue will generate a
discussion that is as heated as the one we had for the 1.0.0 release. However,
it might we worth a few thoughts. My proposal would be as follows:
PLIB based maintenance release: 1.0.1
OSG based main release: 1.1.0 (or 1.2.0)
The rationale being that the old plib version only increases in minor version
to indicate that this is strictly a bugfix release.
The OSG branch will ultimately become version number 2.0.0, but to indicate
that we're not there yet, I believe that it would be a good idea to spawn off
a new intermediate version number to indicate this fact.
I know, in essence, a number is just a number. However, these version numbers
have adopted some symbolic meaning over the years, and the scheme above seems
to reflect our current state of development with reasonable accuracy IMHO.
Thoughts / Questions?