>From Linux Tools project POV our historical data is so unreliable that it >doesn't matter and clean start is not a problem.
Alexander Kurtakov Red Hat Eclipse team ----- Original Message ----- > From: "Thanh Ha" <[email protected]> > To: [email protected] > Sent: Thursday, August 14, 2014 5:33:47 PM > Subject: [cross-project-issues-dev] Bug 438856 - Make Sonar a Foundation > managed service > > Attention Sonar users! > > We have a new Sonar system setup as part of bug 438856 of turning Sonar > into a Foundation managed service. We had to switch because the original > Sonar instance was not using the same type of Database backend as we use > at Eclipse. > > I would like to look into what kind of impact it would have to projects > if we switched the Sonar instances. My understanding is if most projects > do not need or care about the historical Sonar data then a service > switch should be pretty simple and a project would have to run their > Sonar jobs again once we switch to get new data as the old data will be > gone. This seems to be the easiest and I'd like to go this route if it's > not a problem for anyone. > > But if projects do care about the historical data then we'd have to > think of a transition plan and keep the old instance running while > projects switch over. > > I would like to start this transition the week of August 25th if possible. > > Any thoughts? > > > Thanh > > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > _______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
