(CCing dev as this is quite important)
На 16.06.10 10:31, Filip Koczorowski написа:
I've been checking the progress of SIP Communicator for some time now and
noticed a strange trend of no change in the version number.
Oh, you noticed that too? I thought it was my imagination
I mean come on,
you (the authors) have done a great job and introduced a host of new features
in the last few months only
Thanks a lot for the kind words!
and you still name your app "1.0-alpha3"?! In my
opinion, the least you can do is go bravely for "1.0-alpha4"
Heey ... you know what, that's actually a good idea!
Devs, would anyone object to a shift in the alpha number? If not then I
will try to do this over the weekend.
The current numbering scheme is simply confusing for people like me, wanting
to track your progress.
I completely understand your frustration and very much agree.
And the Roadmap page says "SIP Communicator 1.0 -
Completed in summer 2009", "SIP Communicator 1.1 - Completed in Q4, 2009" and
"SIP Communicator 1.2 - Completed in Q1, 2010". That makes the "SIP
Communicator 1.0-alpha3 nightly builds" available to download even more
confusing for users ("What? I can download only 1.0-a3 when they already
I really like what you've done and please don't take it as whining, I'm
seriously curious - why the "1.0-alpha3" still?
Here's why. Feature-wise, we were actually ready to release the 1.0
described in our roadmap. We even forked an SVN branc, started automated
syncs with trunk and ... then stalled. There are several reasons why
the 1.0 branch never became a release:
* Many of us (me included) felt that what users would perceive from that
branch simply wasn't enough to justify the years of development it had
taken us to get there.
* We very rapidly added features to trunk that made the 1.0 branch pale
* We still had a lot of reliability issues. (Not that we don't now but
there were far more back then).
* We wanted to automate the release process in order to simplify future
releases and we never got around to writing the scripts.
So that's how the 1.0 slowly fell out of scope and how the SC build line
fell into a versionless weightlessness.
Evidently we are quite close to the end of this pattern now. I agree
with your suggestion to increment the alpha number and possibly rename
the roadmap milestones in a way that would seem consistent with our
latest nightly builds.
We can then start planning for a 1.0 again (only this time we are far
too close to having jingle not to wait for it )
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org