May be we are saying the same thing using different words, I'm not sure...
What I am saying is those that download the nightly should remain on the
nightly update repo, those that download the stable should always use the
stable repo..
If that's the same thing then we are on the same line ;-)
On Sun, Mar 13, 2016 at 9:59 PM, Jan Baeyens <jan@xxxxxxxxxx> wrote:
Roberto
I think you say the same thing as I do.
So I don't understand why you advice against the approach.
Best regards
Jantje
Op 13/03/2016 om 21:39 schreef Roberto Lo Giacco:
I would advise against that approach: those having downloaded the nightly
should have the nightly repo set as default, those downloading a stable
should point to the stable. If we deactivate the nightly those having a
nightly will receive an error... We want vast majority of our users to use
the stable, with few brave ones using the nightly
On Sun, Mar 13, 2016 at 2:43 PM, Jan Baeyens <jan@xxxxxxxxxx> wrote:
I think that is a good idea. The easiest way I see to implement this is
as follows:
As soon as we come to a stabelized version we want to release we set
nightly to inactive.
As part of the post processing of a release we set the nightly back to
active.
The benefits I see is that when the release is getting stable more and
more "stable users" will get advised to move to the nightly. Though they
are stable users.
We can still use any build to upgrade to release.
I suggest to add the nightly repo to the product for the nightly builds.People that download the nightly are more likely to also update from
nightly. When we build the release we have to set nightly to inactive.
<a href="https://www.freelists.org/list/eclipse-arduino-dev>
<eclipse-arduino-dev@xxxxxxxxxxxxx>eclipse-arduino-dev@xxxxxxxxxxxxx</a>
