-
Notifications
You must be signed in to change notification settings - Fork 83
-
Version 1
ClosedOct 19, 2021 Last updated over 3 years agoThese are the minimum set of goals necessary for making NailGun via…
These are the minimum set of goals necessary for making NailGun viable as a product.
- Move code from Robottelo to NailGun.
- Create a config file.
- Make NailGun installable.
In addition, as many forseeable breaking changes should be addressed as possible before version 1 is released.
-
Make "beta" quality
ClosedAug 17, 2015 Last updated over 9 years agoNailGun is currently listed as being "pre-alpha" quality. I'd like …
NailGun is currently listed as being "pre-alpha" quality. I'd like to push NailGun forward so that it is more viable than that. I'd like to make NailGun high-quality enough that it can be used by third-parties without hesitation. What are the qualities of a high-quality product?
- Well documented.
- Well tested.
- Stable enough to be forward-compatible with future changes.
- Provides significant utility and is easy to use.
This milestone is much like the "alpha" milestone. However, there are some differences:
- The various entity methods should finally be normalized. (#41) This is an interesting problem that may require several tries to get right, but some good solution should be adopted. If an even better solution makes an appearance in the future, then that's a big enough improvement that it would rightfully warrant a major version bump (e.g. from 1.4.2 to 2.0.0).
- Fix other issues that will affect NailGun's API. For example, #135 will definitely affect the API.
-
Make "alpha" Quality
ClosedJul 27, 2015 Last updated over 9 years agoNailGun is currently listed as being "pre-alpha" quality. I'd like …
NailGun is currently listed as being "pre-alpha" quality. I'd like to push NailGun forward so that it is more viable than that. I'd like to make NailGun high-quality enough that it can be used by third-parties without hesitation. What are the qualities of a high-quality product?
- Well documented.
- Well tested.
- Stable enough to be forward-compatible with future changes.
- Provides significant utility and is easy to use.
The third point about "stable enough to be forward-compatible with future changes" is an interesting one. As #41 shows, there will potentially be an enormous number of methods defined on the various entities. Currently, those methods contain a patch-work of different method signatures and responses. Given the number of methods and the toughness of solving that problem in an elegant way, it should certainly be solved before version 1 is released, and preferably before "beta" is released. However, for "alpha" quality, I think it is reasonable to simply charge that the various entity mixins have a stable design (method signatures will not change, behaviour is sane, methods are easy to work with).
-
Quality Control
ClosedDec 18, 2014 Last updated about 10 years agoCreate documentation and automated tests.