Development using dev pre-release tools

We are developing a website. One of the development tools that we use has an alpha version available for the next version, which includes a number of functions that we really want to use (that is, they will save us from having to run thousands of lines to do almost the same thing in anyway).

I made some preliminary estimates, and I like what I see. The question is, should we actually use it for the real? those. not only evaluate it, actually use it for our development and rely on it?

Like alpha software, it is clearly not yet ready for release ... but then not our own code. This is open source, and we have the skills necessary to debug it, so we could theoretically actually make bug fixes.

But on the other hand, we don’t know what the release schedule is for him (they haven’t published it yet), and although I feel fine with him, I wouldn’t be so sure about his use in production, so if he’s not ready before we do this, it may delay our own launch.

What do you think? Is it worth the risk? Do you have any experience (good or bad) in such situations?

[EDIT] I deliberately did not indicate the language we use or the dev tool in question to keep the scope of the question wide, because I feel that this is a question that can be applied to almost all development environments.

[EDIT2] Thanks to Marian for the very helpful answer. I was hoping for more answers, so I put a reward on this.

+3
source share
4 answers

, , . ( , , , , ). . , - .

, , , . . , .

: , .

.

+3

: . , , , .

, , .

, , , , . , , /. RC: .

+2

.

, (//). -, .

, , ( ) , -, , , .

, -, , .

, , .

+2

This is just a risk management issue. In open source, an alpha release can mean many different things. You must be prepared:

  • change the API API;
  • provide bug fixes and workarounds;
  • Test stability, performance, and scalability yourself
  • tracks changes much closer and decides whether to accept more;
  • track the progress they make and respond to fixes / problems.

You use continuous integration, right?

+2
source

Source: https://habr.com/ru/post/1767196/


All Articles