[sip-comm] Sip Communicator version number


#1

Hi,
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. 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 and you still name your app "1.0-alpha3"?! In my
opinion, the least you can do is go bravely for "1.0-alpha4" :wink:

The current numbering scheme is simply confusing for people like me, wanting
to track your progress. 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
finished 1.2?!").

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?

···

--
regards,
Filip

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#2

(CCing dev as this is quite important)

Hey Filip,

На 16.06.10 10:31, Filip Koczorowski написа:

Hi,
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 :wink:

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" :wink:

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
finished 1.2?!").

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
in comparison.

* 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 :slight_smile: )

Cheers,
Emil

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

All,

Just updated the Roadmap with the new version numbers. All that's left
is to bump the alpha up.

We can then start discussing the actual content of the 1.0 release.

Cheers,
Emil

На 18.06.10 23:48, Emil Ivov написа:

···

(CCing dev as this is quite important)

Hey Filip,

На 16.06.10 10:31, Filip Koczorowski написа:

Hi,
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 :wink:

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" :wink:

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
finished 1.2?!").

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
in comparison.

* 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 :slight_smile: )

Cheers,
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

I remember getting hung up on releasing version 1.0.0 of Oscar and even Felix...in reality, it is better just to go ahead and do it and start getting feedback from users and releasing new versions including feedback, etc. No real point in waiting, it's just a psychological barrier...

Release early and often!

-> richard

···

On 6/18/10 17:48, Emil Ivov wrote:

(CCing dev as this is quite important)

Hey Filip,

На 16.06.10 10:31, Filip Koczorowski написа:
   

Hi,
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 :wink:

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" :wink:
     

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
finished 1.2?!").

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
in comparison.

* 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 :slight_smile: )

Cheers,
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#5

Oh, and forgot the link:

http://sip-communicator.org/roadmap

На 19.06.10 00:02, Emil Ivov написа:

···

All,

Just updated the Roadmap with the new version numbers. All that's left
is to bump the alpha up.

We can then start discussing the actual content of the 1.0 release.

Cheers,
Emil

На 18.06.10 23:48, Emil Ivov написа:

(CCing dev as this is quite important)

Hey Filip,

На 16.06.10 10:31, Filip Koczorowski написа:

Hi,
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 :wink:

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" :wink:

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
finished 1.2?!").

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
in comparison.

* 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 :slight_smile: )

Cheers,
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#6

Emil, thank you very much for your detailed reply and for such quick reaction!
And I'm eagerly awaiting the 1.0 release :slight_smile:

···

On 19/06/2010, 00:02 Emil Ivov wrote:

All,

Just updated the Roadmap with the new version numbers. All that's left
is to bump the alpha up.

We can then start discussing the actual content of the 1.0 release.

Cheers,
Emil

--
regards,
Filip

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#7

Emil,

double plus good :wink:

Regards,
Werner

···

Am 19.06.2010 00:03, schrieb Emil Ivov:

Oh, and forgot the link:

http://sip-communicator.org/roadmap

На 19.06.10 00:02, Emil Ivov написа:

All,

Just updated the Roadmap with the new version numbers. All that's left
is to bump the alpha up.

We can then start discussing the actual content of the 1.0 release.

Cheers,
Emil

На 18.06.10 23:48, Emil Ivov написа:

(CCing dev as this is quite important)

Hey Filip,

На 16.06.10 10:31, Filip Koczorowski написа:

Hi,
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 :wink:

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" :wink:

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
finished 1.2?!").

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
in comparison.

* 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 :slight_smile: )

Cheers,
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#8

Hi all,

The roadmap is still a bit confusing:
there is two "SIP Communicator 1.0" milestones remaining.

I was wondering if the "SIP Communicator 1.0 - Completed in summer 2009 - not officially released" corresponds to the "alpha3" release? And if the answer is yes, why can't we simply rename it as "alpha3"?

Cheers,
Vincent

···

On 06/19/2010 12:03 AM, Emil Ivov wrote:

Oh, and forgot the link:

http://sip-communicator.org/roadmap

На 19.06.10 00:02, Emil Ivov написа:

All,

Just updated the Roadmap with the new version numbers. All that's left
is to bump the alpha up.

We can then start discussing the actual content of the 1.0 release.

Cheers,
Emil

На 18.06.10 23:48, Emil Ivov написа:

(CCing dev as this is quite important)

Hey Filip,

На 16.06.10 10:31, Filip Koczorowski написа:

Hi,
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 :wink:

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" :wink:

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
finished 1.2?!").

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
in comparison.

* 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 :slight_smile: )

Cheers,
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#9

На 20.06.10 09:56, Vincent Lucas написа:

The roadmap is still a bit confusing:
there is two "SIP Communicator 1.0" milestones remaining.

There. Should be ok now. Thanks for noticing, Vincent!

Emil

···

I was wondering if the "SIP Communicator 1.0 - Completed in summer 2009
- not officially released" corresponds to the "alpha3" release? And if
the answer is yes, why can't we simply rename it as "alpha3"?

Cheers,
Vincent

On 06/19/2010 12:03 AM, Emil Ivov wrote:

Oh, and forgot the link:

http://sip-communicator.org/roadmap

На 19.06.10 00:02, Emil Ivov написа:

All,

Just updated the Roadmap with the new version numbers. All that's left
is to bump the alpha up.

We can then start discussing the actual content of the 1.0 release.

Cheers,
Emil

На 18.06.10 23:48, Emil Ivov написа:

(CCing dev as this is quite important)

Hey Filip,

На 16.06.10 10:31, Filip Koczorowski написа:

Hi,
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 :wink:

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" :wink:

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
finished 1.2?!").

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
in comparison.

* 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 :slight_smile: )

Cheers,
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net