Re: [nebula-dev] Eclipse ICE - nebula version update breaks build

[Wim Jongman <wim.jongman@xxxxxxxxx>]

Hi,

The current state of affairs is that there is no released version of Nebula but only the availability of the latest and the greatest. Before a build is uploaded to the download site it has passed all (available) tests. So I would consider it stable given the amount of commits we get.

I'm not per se looking at NatTable because we have no release plans. So a "stable version" will get old real soon.

How about we do it like Eclipse Orbit.

Beside the daily build, we just stamp out a stable version every quarter or so that is on line for two years.

Cheers,

Wim

On Fri, Sep 5, 2014 at 9:21 AM, Dirk Fauth <dirk.fauth@xxxxxxxxx> wrote:

@Wim

For productive use there should be a stable update site to which products can refer to. Of course customers need to monitor the project activity or at least ask questions in the forum or mailing list if they need assistance.

You might want to take a look at how NatTable is handling this. Although there aree surely also still some improvements possible. :)

On Thu, Sep 4, 2014 at 4:51 PM, Mickael Istria <mistria@xxxxxxxxxx> wrote:

Hi,

Depending on snapshots is not a good idea, because snapshots are volatile by definition. You'd rather depend on a stabler repository that doesn't risk to change that often.
However, I don't know what can be considered as a stable URL for Nebula... Apparently, there's nothing like that yet.

What I'd advise is the following structure:
* http://download.eclipse.org/technology/
** snapshots/ (where the latest CI build would be published, for testing purpose)
** releases/ (home of releases)
*** 1.0.0/  (named releases)
*** 1.0.1/
*** 1.1.0/
*** ....
*** latest/ (would be either a copy of the latest release repo, or some composite files pointing to the latest release repo).

Then consumers could reference a static site http://download.eclipse.org/technology/nebula/release/1.0.1 in their build. Content wouldn't change so they wouldn't be broken. However, with such URLs, customers have to monitor project activity and manually update the .target/products/pom files to get a new version.

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev