Quality Keeps Moving Forward
For quite a long time Quality Central (QC) was our issue tracker. It was first developed as an in-house method of collecting and managing issues. Since its launch the internal teams have moved to JIRA, and a pump was set up to pull bugs from QC and post them to the internal JIRA. Unfortunately it didn't always synchronize data both directions very well.
A few years ago we started the new Quality Portal which is a public facing JIRA instance. This makes it much easier to synchronize with the internal development process. After the new Quality Portal came on line, we switched QC to readonly and let everyone know it would be retired eventually.
That day has arrived. QC now redirects to the new Quality Portal for the web interface. We still have the database, backend and web services available, but that is no longer publicly facing. Having two issue trackers created confusion, so this simplifies things considerably as now the Quality Portal is the only place to to track issues externally.
Both the old QC and the new Quality Portal feed into the same internal system. But QC and QP were never synchronized. So you will not find the old QC data in QP, but that data is available internally for our bug tracking.
This is part of our process of cleaning up and shutting down some of the old web sites and web services. Some other things to keep an eye on is we are moving from CodeCentral to GitHub and GetIt for most of our code and package sharing (CodeCentral will still be around for a while for registered user downloads, but more and more of that will be through GetIt). We have our new Community site which is replacing the old EDN. And we are slowly rolling out a Slack chat for discussions.
Quality keeps moving forward.
Please login first in order for you to submit comments
- Page :