I was thinking more like a cut of the old Wiki and JIRA than a migration of
the existing stuff.
I think it would be easier and more transparent for folks to handle future
development (if it will happen) by using GitHub.
We may migrate some wiki stuff someday, don't know.
Thanks,
Olaf
--
Sent
> Do we know if it possible it import all historical JIRA issues ...
I don't know it this is possible.
> JIRA has a number of significant benefits over GitHub issues including
> better searching and querying
JIRA is probably more powerful but I guess the simplicity of GitHub is the
greater
> Are we going to say that we won't fix any of the bugs currently open in
JIRA?...
> My concern is having two active bug bases...
We maybe could set or treat or freeze JIRA as read-only and could link to
the entire Flex-JIRA from GitHub in order to not losing the history.
If somebody is going to
Are we going to say that we won't fix any of the bugs currently open in JIRA?
That might be ok. It would help prioritize and make more clear what folks are
still interested in. My concern is having two active bug bases. You may still
end up referencing the JIRA bugs when marking new bugs as
Hi,
> I think it would be easier and more transparent for folks to handle future
> development (if it will happen) by using GitHub.
i’m that sure that it is. JIRA has a number of significant benefits over GitHub
issues including better searching and querying. (Yes I use both).
Do we know if
> It looks like they have started doing something
Yes, seems to be done ;-)
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
It looks like they have started doing something cause I was added to gitbox
Flex repository as a committeer :)
On Mon, Jan 7, 2019, 8:31 PM Olaf Krueger wrote:
> Since nobody has objections I've created the Jira for INFRA:
>
> https://issues.apache.org/jira/browse/INFRA-17574
>
> Olaf
>
>
>
>
That's ok for me, thanks! :)
About the old flex wiki, I think we still have some good info about FlexJS
still not migrated to Royale. I assume all this migration is not about all
of that right?
thanks!
El mar., 8 ene. 2019 a las 10:10, Olaf Krueger ()
escribió:
> Hi,
> I would like to create
I'm not opposed, but I'm not sure it is worth it. I think there are a 800+
bugs filed since Flex came to Apache that are still open in JIRA so JIRA is
known to our Flex users. Not sure if it will be confusing to have two places
to look and I don't think we should migrate those bugs either.
Hi,
the repositories are moved to GitBox [1].
Daniel from INFRA commented this:
"Repositories have been moved. You'll have to sort out the mess with your
two web site repos yourself, one is an svn clone, one is, I presume, a repo
for a next gen site? Both were called the same thing, which caused
Hi,
I would like to create an INFRA Jira in order to ask them to enable GitHub
"Issues" and the "Wiki" for following repositories:
- flex-tlf.git
- flex-utilities.git
- flex-flexunit.git
- flex-site.git
- flex-external.git
- flex-sdk.git
- flex-blazeds.git
- flex-radii8.git
We
I was notified too that I was added :)
El mar., 8 ene. 2019 a las 10:11, Olaf Krueger ()
escribió:
> > It looks like they have started doing something
>
> Yes, seems to be done ;-)
>
>
>
> --
> Sent from: http://apache-flex-development.247.n4.nabble.com/
>
--
Carlos Rovira
12 matches
Mail list logo
