1142614 - Confirm bugzilla code & website is off CVS

Status: RESOLVED FIXED

(Developer Services :: Legacy VCS, defect)

Description

[Hal Wine [:hwine] use NI!]

bug 985020 says source code off CVS, however there is still lots of traffic to CVS from a bugzilla sounding account.

Ideally disable the polling service, but at least get confirmation from bugzilla team that there is no dependency.

Sample lines from March cvsroot/HISTORY logs (1,295 entries so far this month):
    [root@cvs1 CVSROOT]# grep bzrmirror history | tail
    O5501bb8a|bzrmirror%bugzilla.org|<remote>/teQLP4wUVd|mozilla/webtools/testopia||teQLP4wUVd
    O5501bf0a|bzrmirror%bugzilla.org|<remote>/ieQPGtIYj1|mozilla/webtools/bugzilla||ieQPGtIYj1
    O5501bf0b|bzrmirror%bugzilla.org|<remote>/LnngApW86G|mozilla/webtools/bugzilla|BUGZILLA-4_0-BRANCH|LnngApW86G
    O5501bf0d|bzrmirror%bugzilla.org|<remote>/lpRh74GgNK|mozilla/webtools/testopia||lpRh74GgNK
    O5501c28e|bzrmirror%bugzilla.org|<remote>/7GfsKHaaoq|mozilla/webtools/bugzilla||7GfsKHaaoq
    O5501c290|bzrmirror%bugzilla.org|<remote>/w3W7P10NlI|mozilla/webtools/bugzilla|BUGZILLA-4_0-BRANCH|w3W7P10NlI
    O5501c292|bzrmirror%bugzilla.org|<remote>/rMeM33i6Kz|mozilla/webtools/testopia||rMeM33i6Kz
    O5501c612|bzrmirror%bugzilla.org|<remote>/0ult0Ruj7c|mozilla/webtools/bugzilla||0ult0Ruj7c
    O5501c614|bzrmirror%bugzilla.org|<remote>/ZjGVFX9qOB|mozilla/webtools/bugzilla|BUGZILLA-4_0-BRANCH|ZjGVFX9qOB
    O5501c616|bzrmirror%bugzilla.org|<remote>/vDOgmC92gb|mozilla/webtools/testopia||vDOgmC92gb

:justdave - do you know the status?

Comment 1

[Dave Miller [:justdave]]

That's the bzr mirroring script which is mirroring to cvs everything committed to the 4.0 branch in bzr and git.  I can't vouch for testopia, but Bugzilla's last branch that was generated from cvs code which is still supported (4.0 branch) is due for EOL as soon as Bugzilla 5.0 releases, which is supposed to be soon (but I'm betting on at least a month yet).  My understanding is that cvs-mirror is going to stick around and we're only killing cvs itself so nobody can commit anymore, is that correct?

Comment 2

[Dave Miller [:justdave]]

We apparently don't have a release tracking bug yet, but the following query shows bugs that are blocking the 5.0 final release, and it'll be getting released shortly after that starts showing no results.
https://bugzilla.mozilla.org/buglist.cgi?f1=flagtypes.name&list_id=12087374&o1=equals&resolution=---&query_format=advanced&v1=blocking5.0%2B&product=Bugzilla

Comment 3

[Mark Côté [:mcote]]

At the Bugzilla meeting on March 25, we decided that we are okay with cvs being shut down before 5.0 comes out, since we are very close, and we distribute patches that can be used in the event that we need to do a 4.0 security release after cvs is shut down. We'll be posting an announcement next week.