Opera Dragonfly source now on GitHub

By Patrick H. Laukepatrickhlauke. Wednesday, July 4, 2012 10:02:31 PM

Effective from today, Opera Dragonfly's source code has officially moved from our old Bitbucket repository to a shiny new home over in the Opera Software account on GitHub. This move aims to harmonise and gather Opera's various open source projects into a single, sensible location.

The four repositories that have been transferred are:

The dragonfly repository has three main branches: master, cutting-edge and bugfixes. The HEAD of master will always match the current stable release of Opera Dragonfly at https://dragonfly.opera.com/app/, while the HEAD of cutting-edge matches https://dragonfly.opera.com/app/cutting-edge/. Note that there is no experimental branch – these builds are generated separately, in a temporary repo, as they're often focused on simply testing a particular new feature.

These repositories were converted from Mercurial to git, so their structure and commit history should have all been preserved in the process. The only aspect that hasn't been automagically transferred are the various issues that were posted on Bitbucket. If you have a burning issue that you'd like to see addressed, we'd suggest re-posting it over on GitHub.

Profiler lands on default pathExperimental build with event listener inspection and function source tooltips

Comments

Martin KadlecBS-Harou Thursday, July 5, 2012 9:53:59 AM

Does this mean you are going to use git instead of mercurial for internal work as well? smile

(just asking in case I would end up working for Opera angel )

David Håsätherhzr Thursday, July 5, 2012 9:56:10 AM

Originally posted by BS-Harou:

Does this mean you are going to use git instead of mercurial for internal work as well? smile

Yes, we've switched to Git.

ПавелGemorroj Thursday, July 5, 2012 1:12:16 PM

Congratulations on a successful move to github =)
And where brunch is "cutting-edge"? I see only the "master" and "bugfixes".

David Håsätherhzr Thursday, July 5, 2012 1:38:10 PM

Originally posted by Gemorroj:

And where brunch is "cutting-edge"? I see only the "master" and "bugfixes".

This branch will be created the next time we make a cutting-edge build.

MyOpera team, please fix this!fearphage Thursday, July 5, 2012 3:32:18 PM

Finally! Welcome!

Unregistered user Monday, July 9, 2012 8:43:43 AM

Anonymous writes: 1) Any other reasons for this move, or only harmonization/standardization ? 2) You cant create issues as anonymous anymore :( 3) There is a broken link in main info text (to README file gives 404). Should lead to: https://github.com/operasoftware/dragonkeeper/blob/master/README.md

David Håsätherhzr Monday, July 9, 2012 1:12:11 PM

1) Any other reasons for this move, or only harmonization/standardization ?

Mostly that, but we also benefit from a better tools (e.g. for code reviews) and a bigger community.

2) You cant create issues as anonymous anymore sad

Yea, no idea if GitHub is planning support for this.

3) There is a broken link in main info text (to README file gives 404). Should lead to: https://github.com/operasoftware/dragonkeeper/blob/master/README.md

Thank you, fixed.

Unregistered user Wednesday, July 11, 2012 8:07:34 AM

Anonymous writes: That's a great new feature ! // is any support for popular libraries planned ? JQuery, Mootols,YUI, others ?

Unregistered user Wednesday, July 11, 2012 8:09:50 AM

Anonymous writes: Sorry, this comment was for other post. And thanx for answer.

bibit wiyonobibitw Wednesday, October 24, 2012 2:55:37 PM

how to playing this icons on my blog

thanks

Unregistered user Friday, November 23, 2012 7:56:16 AM

Анонимно writes: Hello, Could anybody explain how to use dragonfly-build-tools to build Opera Dragonfly. (what, where must reside & how to run) Thank you.

Unregistered user Friday, November 23, 2012 7:57:43 AM

Anonymous writes: Hello, Could anybody explain how to use dragonfly-build-tools to build Opera Dragonfly. (what, where must reside & how to run) Thank you.

Write a comment

New comments have been disabled for this post.

Next builds

New features are added to the experimental branch as soon as they're ready. Once tested, they move to the cutting-edge branch as a release candidate. Unless any problems arise, they are then promoted to the stable branch.

To switch to these builds, enter the relevant URL in opera:config#DeveloperTools, save the configuration change and (re-)open Opera Dragonfly.

Useful resources

Source code

Bug reports / feature requests