subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <gst...@gmail.com>
Subject Re: Migrating Subversion issues to ...
Date Tue, 15 Sep 2015 18:02:08 GMT
You can do it. File an INFRA ticket for porting our issues into JIRA, and
note that you have some content for a test load. They do test loads often
for incoming, so they have a runbook for that.

(and post the INFRA ticket here, so others can Watch the ticket if they
like)

Cheers,
-g


On Tue, Sep 15, 2015 at 9:51 AM, Ivan Zhakov <ivan@visualsvn.com> wrote:

> On 15 September 2015 at 14:40, Mark Phippard <markphip@gmail.com> wrote:
> > On Tue, Sep 15, 2015 at 5:59 AM, Bert Huijben <bert@qqmail.nl> wrote:
> >>
> >>                 Hi All,
> >>
> >>
> >>
> >> Here at the hackathon in Berlin we are discussing issue trackers, and
> more
> >> particular how we should eventually move our issues to ASF
> infrastructure.
> >> An old TODO.
> >>
> >>
> >>
> >> Ivan just converted the data of the much smaller Serf issuetracker to
> Jira
> >> for the Apache Serf project, and he offers to perform the migration for
> >> Subversion too.
> >>
> >>
> >>
> >>
> >>
> >> I think we really have 3 options:
> >>
> >> [ ] Keep our issues on Tigris
> >>
> >> [ ] Migrate our issues to a new Bugzilla instance hosted by ASF infra
> >>
> >> [ ] Migrate to the standard ASF Jira installation
> >>
> >>
> >>
> >> In Jira we can keep our existing issuenumbers, while for Bugzilla we
> would
> >> need a separate instance.
> >>
> >>
> >>
> >> Personally I would choose the third option if we aim to keep as much
> >> history as possible (including ascii art and attachments) available
> after
> >> the migration. The information in our issue database is just too
> valuable to
> >> loseā€¦. Even if it will take a few more years to get there.
> >>
> >>
> >>
> >>                 Bert
> >
> >
> > +1 on migration.
> >
> > I would bias the decision in favor of doing the migration over trying to
> > solve every problem and letting another year go by.
> >
> > If Ivan has a working migration for Jira then +1 for that.
> >
> > I think it is a mistake to get hung up on these other issues that are
> > trivial in my opinion.  Monospace vs proportional -- I do not believe
> anyone
> > really cares.  Just let the ascii art get messed up.  Old links not
> working
> > ... not a problem you can solve.  Just move on.
> >
> > I would just migrate the data to Jira, not try to solve all these
> problems
> > and move forward.  I have seen zero evidence in the years I have been
> > involved in this project that anyone really cares about the issue
> tracker.
> > We go out of our way to actively discourage people from using it.  To bog
> > down on migration over relatively small problems would just be a waste of
> > time and effort.  It sounds like you already will be accomplishing a lot
> by
> > keeping issue numbers roughly the same.
> >
> > Take that victory and get this done.
> >
> It seems people generally support idea to move to ASF JIRA. I already
> have some data converted and want to perform *test* import  to ASF
> JIRA. Just to see how it will like. Should I request ASF INFRA team do
> this for us or such request supposed to be created by PMC chair?
>
> --
> Ivan Zhakov
>

Mime
View raw message