Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
What is a release manager?
To give you a good example: Where I work, after it is decided that the product is stable and we do an official release (this is a hosted service), the release manager's job is to make sure that the product remains stable (not allowing destabilizing code checkins) and to decide when another official build should be performed and rolled out into the datacenter. If you want to check code into the code that is under release manager control, you have to go to him and explain what the change does, what its implications are, and why it is important enough to check into the stable code.
Did you google this???
Release management
Release Management is the relatively
new but rapidly growing discipline
within software engineering of
managing software releases.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I have experience with Sequelize and TypeORM. LoopBack looks like a good alternative, so I tested it. But it looks like LoopBack 4 is not a finished product; it barely has the needed features for a production application.
My question is: why the LoopBack team decided to publish an unfinished product?
there are a lot of companies and products on live using Loopback4.
Which features you missed from the new version?
I mean, the product is free, open source and built off of previously released, finished products. Releasing it allows them to both test functionality and be provided with feedback and aid in building the actual application. Lots of products are released before they are finished for these important reasons. If you read the documentation, it is a community built product.
Most frameworks are constantly being updated to add functionality, so 'finished' is not really a word that can be thrown around for a framework
While it is not finished, to say it barely has the needs to support a production application is very dependent on the type of application being built.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
From my understanding, the EAP version has the ultimate features included in it.
I am curious whether this version can be used for commercial use.
I have no been able to find a definite answer. Thanks.
Yes. If you look at the IDEA*.txt licenses in the <ideaInstallDir>/license directory of an EAP version, you will see that they are exactly the same as those in the released version. Basically EAP's are considered evaluation licenses (see comment by JetBrains here). If you (or your lawyers) want to be absolutely sure, I recommend e-mailing sales#JetBrains.com
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am in the process of evaluating whether BigQuery could be a good choice for some data processing we want to run periodically.
I do appreciate that BigQuery is still under heavy development and that improvements and fixes are likely to happen pretty often.
I woud like to know what would be the process should a release break a previously working process. I have read the SLAs, but they seem to be more oriented to downtime, rather than regression issues/bugs. Is there an option for paid support with SLAs?
Like most commercial services, Google applies rigorous build and test processes to ensure quality. If you have specific support requirements, we encourage you to contact Google's Cloud Platform sales team to discuss our premier offering.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
Are there any best practices to keep in mind while designing API's which ensures backward compatibility and new version releases. Any links to articles/blogs is appreciated.
You should check out this presentation about API design. It's from Google and pretty good.
It also addresses backward compatibility and new releases.
How to Design a Good API and Why it Matters
keep both running, with version in the url. api.mysite.com/[version]/api/url/here. Notify the users when a new version of the API arrives, and drop the old version after a while. Either when it isn't used anymore, or like 6 months insuring the users had enough time to change it.
Or keep it running forever, but don't deliver any new functionality for it.
The best way to do this to keep the old interface or class in new release with new interface and classes and marked them as deprecated (means those will be removed in future release).
Hear API designer keep in mind about difference between public interface and published interface.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I am trying to use Jira for requirement as well as bug tracking. How do I add requirements into Jira?
My organization uses Issues to track top-level features (usually on support development) and then Subtasks to those Issues for individual requirements. An Issue might be "Linking not working as intended" with a subtask of "Write a new stored procedure to handle blanks."
For new development, you might check out the Agile module for JIRA. We have it, but I am not currently on the project that uses it.
An obvious solution is to use "Issue Type" to distinguish Bugs/Requirements.
Or maybe you could try adding a phony version "BACKLOG" where all requirements go first. Then put approved requirements into a planed sprint version (e.g. "R2011-S1"). This is a work-around when you do not have the Agile extension.