Release candidate

[MicheleVilla]

Hi
before every official release of last version of OpenTx I think may be usefull to create a Release Candidate for bugs hunting.
In this case some users know that is a non stable version but they can help to find bugs
In the past in some cases a bug was discovered immediately after release forcing the developers to quickly release a new version.

[frater]

That's a good idea. It will also give these early adopters an incentive to immediately report them. As a side note. At this moment the Europeans are in real need of 2.016's ability to flash Frsky equipment due to the new Jan 2015 regulations for 2.4 GHz.

[Kilrah]

Nonstable nightlies are available at all times, both for the 2.0 and 2.1 branches.
http://jenkins.open-tx.org/nightly-20/
http://jenkins.open-tx.org/nightly-21/

We usually try to do a heads-up before release, but in the past that hasn't really sparked much interest, most say "I'll try it", but when we release a few days later they didn't have time yet

[OctavioS]

Is there a place to follow openTX new features or development, just to know whats going on?

[jtaylor]

>Is there a place to follow openTX new features or development, just to know whats going on?

https://github.com/opentx/opentx

https://github.com/opentx/opentx/milestones

[Kilrah]

Look at the issues related to the milestones, and the commits. Developers tend to discuss via the comments on github and IM.

https://github.com/opentx/opentx/commits/next (2.1)
https://github.com/opentx/opentx/commits/master (2.0)

[frater]

Nonstable nightlies are available at all times, both for the 2.0 and 2.1 branches.
http://jenkins.open-tx.org/nightly-20/
http://jenkins.open-tx.org/nightly-21/

We usually try to do a heads-up before release, but in the past that hasn't really sparked much interest, most say "I'll try it", but when we release a few days later they didn't have time yet

....A few days is way too short
I have to wait until Friday evening (it's Monday now) until I can get to my radio, let alone flash and try it....

Doing it on Friday and wait until Tuesday for a release would make it possible for me to test it in a weekend.

[Kilrah]

Which is why we've got the nightly builds running all the time, so you can test at any time, not just in the last days. 2.1 release is still several weeks away.

[frater]

Hi Kilrah,
As I wrote before I'm considering to move to 2.1. Mainly because I'm still in the process of learning and I prefer not to invest more time in 2.0.x telemetry if 2.1.x is going to be so much different.
You advised me against actually using it on flying models..

At a certain point this should be possible. Have we already reached that point?

I am of course fully aware of the experimental nature of it, but as long as I keep some control over my model it's fine by me.

[Kilrah]

That point will be reached when it is officially released... Until then you do what you want, but there's no assumption things work correctly and everything you configure on it may be corrupted/lost overnight without warning requiring starting from scratch.

[frater]

Not much to go on here besides taking the plunge. There has to be a point where things have stabilized and it needs more testing before releasing, but could well be working decently.

I just want to hop on it a bit before the release.

[frater]

There are only a few open issues on 2.0.16 and also a few for 2.1.0
Is 2.1.0 a milestone of a release that could be used for flying and could even happen quite soon or am i way off there?

[Kilrah]

Any official release is obviously supposed to be fit for flying. 2.1.0 will be the first release of the 2.1 branch, and as there's a lot of new/changed stuff a beta test period will happen before it gets released.

[Daedalus66]

It seems to me Kilrah has been crystal clear. There' no assurance it's fit to fly until official release. And that only happens after a suitable beta test period.

There is no such thing as "some control over the model"! Or at least nothing that makes sense.

[Daedalus66]

It seems to me Kilrah has been crystal clear. There' no assurance it's fit to fly until official release. And that only happens after a suitable beta test period.

There is no such thing as "some control over the model"! Or at least nothing that makes sense.

[frater]

It seems to me Kilrah has been crystal clear. There' no assurance it's fit to fly until official release. And that only happens after a suitable beta test period.

I found the answer I was looking for and I'm just trying to find the right moment to switch.

There's no assurance if it's fit to fly after an official release either as I found out a week after acquiring my first Taranis. Only because I didn't have anything critical on my first logical switch it didn't influence the control of my model. Because I was a complete newbie with this new radio I was blaming myself at first. I merely mentioned it on rcgroups as a question after it happened several times.

So yes, I was having "some control over the model" and not ALL. The radio had its "own ideas".
http://www.rcgroups.com/forums/showthre ... st29825514

Not complaining at all. It goes with the territory. I am very happy with OpenTX and the efforts the current developers are putting into it and the directions they are taking it.

I'm still having problems with the SD-Card, but it seems that bug is squashed for 2.0.16.

It's not that I want the "latest and greatest". In this case I want to start the upcoming flying season getting used to the new telemetry system. I don't want to "invest" into the current system too much.
I can take full responsibility for my own actions.