Hm... I don't think we need more than 1 projects, setup and so on, can be all part of 1 thing.
On Thu, Sep 25, 2014 at 4:07 PM, Andre Klapper aklapper@wikimedia.org wrote:
Heja,
On Thu, 2014-09-25 at 14:57 +0200, Petr Bena wrote:
Yes, I wrote you yesterday during that phabricator conference, but you probably overlooked it
Ah, now it all makes sense! Sorry, I did not see *anything* written - I just had my browser window (screencasted) in front of me and had to rely on people's spoken words to tell me or forward anything. :)
however Rachel did forward that question to you.
Hmm, hmm. I wonder where. :-(
I was asking how is the migration going to happen, eg. if there would be new project created in phabricator and issues migrated there?
We migrate existing Bugzilla products and components into Phabricator projects: https://phabricator.wikimedia.org/T43 . The "Setup" component in the "Huggle" product will become a "Huggle-Setup" project.
Bugzilla tickets will be imported, see https://phabricator.wikimedia.org/T259 for how Bugzilla UI elements and metadata will end up in Phabricator.
Bugzilla user accounts will be imported and you can reclaim them, see https://www.mediawiki.org/wiki/Phabricator/Help#Claiming_your_previous_Bugzi...
However as a maintainer/developer/interested users you will likely have to manually "join" the Huggle project(s) in Phabricator and become a member, in order to receive task notifications.
What about versions etc.
There will not be an equivalent of Bugzilla's "Version" field in Phabricator (it seems that Huggle is the only project really using it in Bugzilla). If the Version field was not empty in a Bugzilla ticket, the imported ticket will include the value of the Version field in the initial description of the Phabricator task.
What's "etc" in this context? :)
Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/
Huggle mailing list Huggle@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/huggle