[sip-comm-dev] Adding one more new feature to the rc-1.0 list


#1

Hey folks,

Our 1.0 branch (which for the time being coincides with trunk) is
currently closed for new features in an effort to make sure that we'll
be heading toward a stable 1.0 release that could be used for real-world
deployments.

There is however one more feature that I would like us to consider for
1.0 - auto-updates for windows. We currently have update mechanisms for
Linux (through the native repository mechanisms) and Mac OS X (through
sparkle), and a notifications-only plugin for Windows. I am thinking
that we should have a sparkle-like updater for Windows too. We'd have to
implement it ourselves however, since I am not aware of similar generic
libs that we could use for windows.

The reason why I'd like us to include this to 1.0 is so that we could
make sure that users who decide to give SC a try from the start, could
easily benefit from fixes and new features.

The downside of course is that this would add delay to our release date
(so to speak, since we don't have a specific date set).

Thoughts?

Emil

···

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


#2

Hi Emil,

It's been a long time I did not use windows so I was wondering whether such automatic update features are common in windows' software? I may have the wrong impression that windows users are used to download new software versions from the web every new release :slight_smile:

But I agree this is an important feature, plus having the same set of features among the various OS versions is important too. I'd vote in favour of adding it to the RC1 feature list. Do you know anyone who would be willing working on this?

cheers,
romain

···

On 2009/03/04, at 11:37, Emil Ivov wrote:

Hey folks,

Our 1.0 branch (which for the time being coincides with trunk) is
currently closed for new features in an effort to make sure that we'll
be heading toward a stable 1.0 release that could be used for real-world
deployments.

There is however one more feature that I would like us to consider for
1.0 - auto-updates for windows. We currently have update mechanisms for
Linux (through the native repository mechanisms) and Mac OS X (through
sparkle), and a notifications-only plugin for Windows. I am thinking
that we should have a sparkle-like updater for Windows too. We'd have to
implement it ourselves however, since I am not aware of similar generic
libs that we could use for windows.

The reason why I'd like us to include this to 1.0 is so that we could
make sure that users who decide to give SC a try from the start, could
easily benefit from fixes and new features.

The downside of course is that this would add delay to our release date
(so to speak, since we don't have a specific date set).

Thoughts?

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


#3

Hi Romain,

I think a notable part of the third-party software installed on my
Windows does automatic update checking and prompts me to download and
install the new version for me e.g. Mozilla Firefox, VLC,
uTorrent/BitTorrent, Eclipse. And there's always Windows Update taking
care of the software Microsoft installed as part of Windows. So I'd
say the automatic updates on Windows are becoming common to me and I
think they are an important feature.

I also agree with you on the point of cross-platform consistency.

To sum it up, I vote in favor of adding it to the RC1 feature list.

As to the availability of contributors, I think this feature is simple
enough to participate in the upcoming Google Summer of Code and offers
an easy way for newcomers to make a contribution without delving deep
into the project. If push comes to shove, I can try it myself.

Best regards,
Lubo

···

On Thu, Mar 5, 2009 at 1:14 PM, Romain KUNTZ <kuntz@lsiit.u-strasbg.fr> wrote:

Hi Emil,

It's been a long time I did not use windows so I was wondering whether such
automatic update features are common in windows' software? I may have the
wrong impression that windows users are used to download new software
versions from the web every new release :slight_smile:

But I agree this is an important feature, plus having the same set of
features among the various OS versions is important too. I'd vote in favour
of adding it to the RC1 feature list. Do you know anyone who would be
willing working on this?

cheers,
romain

On 2009/03/04, at 11:37, Emil Ivov wrote:

Hey folks,

Our 1.0 branch (which for the time being coincides with trunk) is
currently closed for new features in an effort to make sure that we'll
be heading toward a stable 1.0 release that could be used for real-world
deployments.

There is however one more feature that I would like us to consider for
1.0 - auto-updates for windows. We currently have update mechanisms for
Linux (through the native repository mechanisms) and Mac OS X (through
sparkle), and a notifications-only plugin for Windows. I am thinking
that we should have a sparkle-like updater for Windows too. We'd have to
implement it ourselves however, since I am not aware of similar generic
libs that we could use for windows.

The reason why I'd like us to include this to 1.0 is so that we could
make sure that users who decide to give SC a try from the start, could
easily benefit from fixes and new features.

The downside of course is that this would add delay to our release date
(so to speak, since we don't have a specific date set).

Thoughts?

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

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