Carrot2

Update mechanism

Details

  • Type: New Feature New Feature
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: 3.4.0
  • Component/s: Document Clustering Workbench
  • Labels:
    None

Description

The 3.x version is days from receiving Stable status. People will start to download Workbench, play with it, report bugs and ask for improvements. Update mechanism will come really in handy once it starts. At the beginning it will be enough to provide 'update on demand' - user has to initiate it. Later it would be nice touch to add auto-update option, e.g. every Monday.

What do you guys think?

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dawid Weiss added a comment -

I guess it comes down to: is this a lot of work?

Show
Dawid Weiss added a comment - I guess it comes down to: is this a lot of work?
Hide
Permalink
Urszula Krukar added a comment -

Update mechanism in Eclipse is very well documented with lots of sample code - not a lot of work here. But I suspect it will require build changes (adding suffix to version number). Plus, you're going to have to think of Carrot's versioning strategy - in order for update to work, version numbers need to change every once in a while.

Show
Urszula Krukar added a comment - Update mechanism in Eclipse is very well documented with lots of sample code - not a lot of work here. But I suspect it will require build changes (adding suffix to version number). Plus, you're going to have to think of Carrot's versioning strategy - in order for update to work, version numbers need to change every once in a while.
Hide
Permalink
Dawid Weiss added a comment -

Version numbers are already part of the distribution and are used in Maven artefacts. We version stable builds only, no snapshots are available. This said, resulting files do not have a version number appended to them, as it is the practice in Eclipse (and I would rather not have this in our releases – it is rather odd).

Show
Dawid Weiss added a comment - Version numbers are already part of the distribution and are used in Maven artefacts. We version stable builds only, no snapshots are available. This said, resulting files do not have a version number appended to them, as it is the practice in Eclipse (and I would rather not have this in our releases – it is rather odd).
Hide
Permalink
Stanisław Osiński added a comment -

To be honest, I'd wait with implementing updates until we have some knowledge of how frequently people use Workbench and how frequently they need to update. My experience with Eclipse update is that it's sometimes easier to download the new ZIP rather than try to update (which is probably more of a plugins' than Eclipse's fault). To sum up, I'd reschedule this to 3.1.

Show
Stanisław Osiński added a comment - To be honest, I'd wait with implementing updates until we have some knowledge of how frequently people use Workbench and how frequently they need to update. My experience with Eclipse update is that it's sometimes easier to download the new ZIP rather than try to update (which is probably more of a plugins' than Eclipse's fault). To sum up, I'd reschedule this to 3.1.
Hide
Permalink
Dawid Weiss added a comment -

Agree here. I've never been able to update Eclipse between major revisions with success.

Show
Dawid Weiss added a comment - Agree here. I've never been able to update Eclipse between major revisions with success.
Hide
Permalink
Dawid Weiss added a comment -

Won't fix this. We don't need an update mechanism, especially now with all the P2-related mess.

Show
Dawid Weiss added a comment - Won't fix this. We don't need an update mechanism, especially now with all the P2-related mess.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Carrot2. Try JIRA - bug tracking software for your team.