Ahoj Petr,
On Thu, 2014-09-25 at 09:05 +0000, Petr Bena wrote:
Bugzilla is going to be shut down
Unfortunately, my favorite BT is going to be replaced with phabricator, it will happen soonish and for 3 days we are going to be without a bug tracker, you can use the tracker we have on github in case you needed to report any issues meanwhile.
I will give you more information as soon as I get more information :) I can't really get much out of Andre regarding how the migration is going to work.
You might want to consider contacting me if you'd like to get something out of me? :)
Please do ask all the things which feel unclear to you, preferably on https://www.mediawiki.org/wiki/Talk:Phabricator
And in general, there's some information that can be found on https://www.mediawiki.org/wiki/Phabricator - but it's work in progress and we are very happy to improve it based on feedback!
Cheers, andre
Hey Andre,
Yes, I wrote you yesterday during that phabricator conference, but you probably overlooked it, however Rachel did forward that question to you. I was asking how is the migration going to happen, eg. if there would be new project created in phabricator and issues migrated there? What about versions etc.
I didn't get very clear response, hence this comment in my first mail. But I guess I will have to wait for a final switch to see how it's going to work.
On Thu, Sep 25, 2014 at 2:31 PM, Andre Klapper aklapper@wikimedia.org wrote:
Ahoj Petr,
On Thu, 2014-09-25 at 09:05 +0000, Petr Bena wrote:
Bugzilla is going to be shut down
Unfortunately, my favorite BT is going to be replaced with phabricator, it will happen soonish and for 3 days we are going to be without a bug tracker, you can use the tracker we have on github in case you needed to report any issues meanwhile.
I will give you more information as soon as I get more information :) I can't really get much out of Andre regarding how the migration is going to work.
You might want to consider contacting me if you'd like to get something out of me? :)
Please do ask all the things which feel unclear to you, preferably on https://www.mediawiki.org/wiki/Talk:Phabricator
And in general, there's some information that can be found on https://www.mediawiki.org/wiki/Phabricator - but it's work in progress and we are very happy to improve it based on feedback!
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
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
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
Who is going to manage that project, eg. being able to change description, links, etc
On Thu, Sep 25, 2014 at 4:39 PM, Petr Bena benapetr@gmail.com wrote:
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
On Thu, 2014-09-25 at 16:40 +0200, Petr Bena wrote:
Who is going to manage that project, eg. being able to change description, links, etc
That depends on permissions... Is that something needed more often? Asking because currently in Bugzilla, I consider project descriptions pretty stable.
andre
On Thu, Sep 25, 2014 at 4:39 PM, Petr Bena benapetr@gmail.com wrote:
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
Huggle mailing list Huggle@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/huggle
On Thu, 2014-09-25 at 16:39 +0200, Petr Bena wrote:
Hm... I don't think we need more than 1 projects, setup and so on, can be all part of 1 thing.
We can always move tickets and merge projects after having migrated the Bugzilla content into Phabricator. We don't handle to deal with specific requests to restructure the taxonomy in the migration logic itself though - it's already complex enough. :)
Cheers, andre
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
Huggle mailing list Huggle@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/huggle