Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • From the standpoint of the continuous integration servers, the library itself is not small and take a couple minutes to build. Commented Feb 29, 2012 at 18:04
  • @RobZ: So? As long as the library doesn't change, you don't need to rebuild it, do you? Commented Feb 29, 2012 at 19:02
  • Right now it is still under active development. Commented Feb 29, 2012 at 19:06
  • @RobZ: Yes, that maybe so, but if the library team is tagging a version every 10 minutes then they're doing it wrong. Continuous integration is a nice thing, but a release should comprise some sort of usability testing. In the case of a library, that's a code review. This can't be automated. However the process of you getting the last reviewed and tagged version can be automated, and if reviews are done properly and tagging is done responsibly, then I don't see an issue, but actually an enhancement. Commented Feb 29, 2012 at 19:45