I've conflated "os" labels to All, macOS, Windows, Linux (full OS is
present in text),
I've removed the severity label completely (it is in text only). I keep
just "enhancement" and "regression" as labels.
I've simplified priority labels. They are P1, P2, ... instead of "priority:
P1", "priority:
Firstly, thanks for all your work on this!
1) I agree, we should combine them (if it's not too much effort).
The exact details e.g. versions (and architecture) should be in the bug anyway?
Or maybe, remove them completely (just keep it in the text)?
Does anyone use them for filtering?
2) I would
Update:
* I've implemented Bugzilla milestones -> GitHub milestones conversion
* I've added links to GitHub profiles
* I've removed issue headers, and moved attachments to comment footers, so
issues look pretty much the same as if they were manually created at GitHub
* I've removed "bugzilla"
Hi Vladimir,
I review the doc, looks good for me (+1). Thanks for you work.
Milamber
On 05/08/2022 11:31, Vladimir Sitnikov wrote:
I've created a draft migration plan, comments are welcome:
I've created a draft migration plan, comments are welcome:
https://docs.google.com/document/d/1kUN9wMFR1CEydq345Nh_ohrPkCsQdaHjSUYpPAUfw6I/edit#heading=h.xm5w7ls8nz2w
https://issues.apache.org/jira/browse/INFRA-23553
Vladimir
Some updates: I've implemented cross-references (duplidates, duplicated by,
depends on, blocks)
On top of that, every "bug 2323" mention is replaced with GitHub URL, so
navigation between issues works.
Here's a sample issue: https://github.com/vlsi/tmp-jmeter-issues/issues/1188
The import takes
Drew from Infra fetched and sanitized the dump, and I was able use it
directly instead of fetching the data from UI.
I ran the first import, and here's how it looks:
https://github.com/vlsi/tmp-jmeter-issues/issues
It looks more-or-less fine to me.
Note: last time I imported, there was a
I've raised https://issues.apache.org/jira/browse/INFRA-23475 to fetch
Bugzilla dump.
Vladimir
>* Maybe we could dump the data from the MySQL database, import in into a
clone and work from that instance instead through the UI?
This might indeed be a better idea. It is great I did not invest much time
in scraping the UI.
The sad thing is the dump contains sensitive information, so I would
Am 11.07.22 um 17:50 schrieb Vladimir Sitnikov:
I've made progress on Bugzilla -> GitHub migration.
Frankly speaking, I'm not comfortable refactoring/maintaining Python code
(which is what many projects use to migrate off Bugzilla),
so I created Kotlin-based project so the data and fields are
I've made progress on Bugzilla -> GitHub migration.
Frankly speaking, I'm not comfortable refactoring/maintaining Python code
(which is what many projects use to migrate off Bugzilla),
so I created Kotlin-based project so the data and fields are typed:
https://github.com/vlsi/bugzilla2github
For
>That's a annoying if my understanding is correct, how do we distinguish
>reporters comments from dev/committers ones ?
Comments on GitHub would start with "${username} commented: ${comment}"
>Does it means bugzilla would still be up ? What is the point then ?
It will be read-only for
Hello,
Find my answers inline below.
Regards
On Tue, Dec 28, 2021 at 7:34 AM Vladimir Sitnikov <
sitnikov.vladi...@gmail.com> wrote:
> Unfortunately, infra says GitHub can't help us with the migration:
> https://issues.apache.org/jira/browse/INFRA-22618
>
> So what we can do is to follow
>
Unfortunately, infra says GitHub can't help us with the migration:
https://issues.apache.org/jira/browse/INFRA-22618
So what we can do is to follow
https://github.com/Quuxplusone/BugzillaToGithub
The downsides would be:
a) All comments will be authored by the "asf-git" (or a similar bot-like
I'm inclined to "Bugzilla -> Gitlab -> GitHub" approach, so I asked INFRA
if they can help with requesting GitHub support:
https://issues.apache.org/jira/browse/INFRA-22618
Does anybody want to try https://github.com/llvm/bugzilla2gitlab/tree/llvm
with JMeter's Bugzilla?
Gitlab could probably be
It looks like LLVM migration to GitHub is done.
The approach is described in
https://groups.google.com/g/llvm-dev/c/vum4_czZ13E/m/o4kxxOgQCAAJ
What they did was they migrated Bugzilla -> Gitlab, and then they used
GitHub Enterprise Migration API to migrate from Gitlab dump to GitHub.
Gitlab
Just in case, LLVM is migrating issues from Bugzilla to GitHub Issues:
https://llvm.discourse.group/t/bugzilla-migration/4848
I guess we could approach the LLVM team after they migrate.
They collected GitHub ids via Google form.
Basically, they asked to submit their "email -> github login" pairs,
Hi,
For me, it is important to have as few switches as possible. Ideally, jira
was used and integrated with other tools, e.g. bittbucket + confluence (
https://cwiki.apache.org/confluence/display/JMETER/Home ). But since the
code is already in git and discussions can be held there ( reducing the
Nice.
It looks like it might be worth trying GitHub issues.
>but what happens if at some step we have to leave github
INFRA team has scripts for importing GitHub history to ASF JIRA.
Any thoughts on the migration of the old issues?
Do we need to migrate comments from Bugzilla to GitHub
Hello,
My discussion "vote" is
+1 keep Bugzilla (not much work for me, and it works for me really well)
-1 JIRA (I find it very slow last time I used it)
+1 Github Issues (but what happens if at some step we have to leave github
provided we don"t loose bugzilla history)
Regards
Philippe
On Thu,
My discussion "vote" is
+1 keep Bugzilla (not much work for me, and it works for me really well)
-0.8 JIRA (I find it difficult to use)
+0.5 Github Issues (they seem to be lightweight enough to be
understandable by me, but I fear, that we would loose a lot of old
issues (which might be a good
my vote
0 keep using Bugzilla
+1 migrate to GitHub Issues
+0.5 migrate to ASF JIRA
On Thu, Nov 25, 2021 at 12:10 PM Vladimir Sitnikov <
sitnikov.vladi...@gmail.com> wrote:
> Hi,
>
> Does anybody have a strong opinion regarding Bugzilla vs JIRA vs GitHub
> issues?
>
> Frankly speaking, I am
22 matches
Mail list logo
