在生产中使用稳定的Bootstrap v 5

Today, we managed to release a stable free version of Material Design for Bootstrap 5 UI Kit — even though Bootstrap itself is still in its Alpha version.

牛逼 ODAY，我们成功地释放出材料设计的自举5 UI工具包稳定的免费版本 -尽管引导本身仍处于Alpha版本。

How exactly?

到底如何

I’ll answer that in a minute but first — we need to talk about versioning, choosing tools and software testing…

我会在一分钟内回答这个问题，但首先-我们需要谈论版本控制，选择工具和软件测试…

Whenever assessing a new library, framework, or any other tool for a serious web project the first question you should ask yourself is:

w ^ henever评估一个新的图书馆，框架，或任何其他工具，一个严重的网络项目，你应该问自己的第一个问题是：

Is that stable?

那稳定吗？

Ok, but what stable really means?

好的，但是稳定到底意味着什么？

For the longest time ever stable used to mean that there will be no further changes added to the software.

在过去最长的时间内， 稳定意味着没有对该软件进行进一步的更改。

But as we all know, in case of web development — there are always changes added to the software.

但是众所周知，在进行Web开发的情况下- 总是会在软件中添加更改。

Code & web environment in XXI century is simply changing too fast to assume that the current version will work forever — that’s almost never the case.

XXI世纪的代码和Web环境变化太快，以至于无法假定当前版本将永远有效-几乎从来没有。

Therefore, the definition seemed to change a bit and currently if you’d like to label your software as “stable” it needs to fulfill 3 basic conditions:

因此，定义似乎有所变化，当前，如果您想将软件标记为“稳定”，则需要满足以下三个基本条件 ：

1First, and foremost:Stable = Ready for production use

1首先，也是最重要的： 稳定=可供生产使用

There’s no more important indicator than this one. If you cannot guarantee that your app/library/plugin/other type of software, is ready to be used in real-life projects, don’t mark it as stable.

没有比这更重要的指标了。 如果您不能保证您的应用程序/库/插件/其他类型的软件可以在实际项目中使用，请不要将其标记为稳定。

Of course, there’s nothing wrong in selling a Beta or even an Alpha version of a product — as long as the price is adequate and your customer is aware of possible issues.

当然，只要价格合理并且您的客户知道可能出现的问题，出售Beta版本甚至Alpha版本的产品就没错。

That’s actually what we did.

这实际上就是我们所做的。

We started selling the premium version of MDB5 when it was still in Beta.

当MDB5仍处于Beta版时，我们开始出售其高级版本。

This was limited to trusted users that shared their feedback with us in the past so we knew that their insight would be valuable.

这仅限于过去与我们共享他们的反馈的受信任用户，因此我们知道他们的见解将是有价值的。

But even for them— we always highlighted that it is still a Beta version, and if they use it for any serious project we won’t bear the responsibility for the issues. We achieved a few things, this way:

但是即使对他们来说，我们始终强调它仍然是Beta版本，如果他们将其用于任何严肃的项目，我们将不承担任何责任。 通过这种方式，我们取得了一些成就：

• The users were 100% ok with using a Beta version for a lower price
  用户以较低的价格使用Beta版本可以100％确定
• We gathered 326 detailed improvement requests
  我们收集了326条详细的改进要求
• The users were excited to be a part of the development process
  用户很高兴成为开发过程的一部分

Ok, but how do I now when my software is ready for production?

好的，但是当我的软件可以投入生产时，我现在该怎么办？

This is a great question! And it brings us to part 2.

这是一个很好的问题！ 它把我们带到了第二部分。

2Second, condition:A stable version should be tested AF

2二，条件： 应测试稳定版AF

Please, pardon my french but I cannot stress this enough.

拜托，请原谅我的法语，但我对此压力还不够。

A stable version of any type of software (not only web-dev related), should be tested thoroughly, then tested again by somebody else, and then probably tested 10 more times…

任何类型的软件(不仅是与Web开发相关的软件)的稳定版本，都应该进行彻底测试，然后再由其他人进行测试，然后可能还要再测试10次……

The sentence above is part-exaggeration, part-true. Of course, the testing process and success conditions will vary for every product.

上面的句子部分夸张，部分真实。 当然，每种产品的测试过程和成功条件都会有所不同。

There’s no one-size-fits-all solution for this one so we’ll simply list the thing that we did to make sure that MDB5 is well tested:

对于这一解决方案，没有一个万能的解决方案，因此我们只列出我们为确保MDB5受到良好测试而做的事情：

• Every component had a detailed specification
  每个组件都有详细的规范
• We created Unit Tests with at least 80% coverage
  我们创建的单元测试的覆盖率至少为80％
• Every component had to go through 3 test types (JavaScript, Design & Documentation tests)
  每个组件都必须经过3种测试类型(JavaScript，设计和文档测试)
• We responded to reported issues immediately
  我们立即回复了已举报的问题

• We’ve been performing those test constantly for 3 months

  我们已经连续进行了3个月的测试

Of course, this is an arbitrary list — 3 months of testing and 80% coverage and is a great result for a JavaScript UI Kit, but if you’re creating a payment app or medical software — you need a lot more time, and there’s no need to explain why.

当然，这是一个任意列表-3个月的测试和80％的覆盖率，对于JavaScript UI Kit来说是一个不错的成绩，但是，如果您要创建付款应用程序或医疗软件，则需要更多时间，并且无需解释原因。

3 Last but not least:Stable should be backward compatible

3最后但并非最不重要的一点： 稳定状态应向后兼容

With Alpha and Beta versions you have a margin of error — if you introduce any solution that will break earlier features — that’s not a problem, you simply scratch those features and move on.

对于Alpha和Beta版本，您有一定的误差-如果您引入任何会破坏早期功能的解决方案-这不是问题，您只需刮擦这些功能并继续。

That’s not something you can do with a stable version.

使用稳定版本无法做到这一点。

Of course, you can introduce new updated features, patches, bug fixes etc. but none of them can impact previously released functionalities.

当然，您可以引入新的更新功能，补丁，错误修复等，但是它们都不会对先前发布的功能产生影响。

And how did you do that with Bootstrap in early alpha?

以及您如何使用早期Alpha版的Bootstrap做到这一点？

That’s simple — in MDB 5, we mostly use our own solutions, taking from Bootstrap only what is already stable and tested.

这很简单-在MDB 5中，我们主要使用自己的解决方案， 仅从Bootstrap中获取已经稳定且经过测试的内容 。

Our goal was to use all the most popular and stable features of Bootstrap, but at the same time not to rely entirely on Bootstrap itself and build as many of our own solutions as possible.

我们的目标是使用Bootstrap的所有最受欢迎和最稳定的功能 ，但同时不要完全依赖Bootstrap本身并构建尽可能多的我们自己的解决方案。

Thanks to this approach (and whole vacation-season spent on testing 😢) we have control over the source code and we can guarantee its stability.

由于采用了这种方法(并且整个假期都花在了测试上)，我们可以控制源代码，并且可以保证其稳定性。

We invite you to test the UI Kit and judge it for yourself: https://mdbootstrap.com/docs/standard/

我们邀请您测试UI Kit并自行判断： https : //mdbootstrap.com/docs/standard/

使用Bit共享，记录和管理来自不同项目的可重用React组件 (Share, document, and manage reusable React components from different projects using Bit)

Bit (Github) makes it quick and easy to share components from any project.

Bit ( Github )使您可以快速轻松地共享任何项目中的组件。

Components shared on the Bit.dev platform, are easy to find with auto-generated documentation and live code examples.

通过自动生成的文档和实时代码示例，可以轻松找到在Bit.dev平台上共享的组件。

Use it to increase code reuse, speed up development, and build apps that scale.

使用它可以增加代码重用，加速开发并构建可扩展的应用程序。

Example: React components shared on Bit.dev

示例：React在 Bit.dev上共享的组件

翻译自: https://blog.bitsrc.io/using-a-stable-bootstrap-v-5-on-production-1d48e393614a