An update about Gitorious v3.0

When we merged the Rails 3 branch into next back in January it was our intention that this would become Gitorious 3.0, with few user-visible features. Our plan was to ship 3.1 shortly after, including the new code browser we started working on last year.

The upgrade to rails 3 was done mainly to enable us to run the code browser asynchronously, and we have put a lot of effort into making it possible to run an asynchronous web server alongside the Gitorious Rails application. Despite these efforts we were never able to get the stability we need with this setup. To make matters worse, the speed benefits from running asynchronously haven’t been as big as we had hoped. Because of this we have decided to make some changes to our plans:

Gitorious 3 will include the new code browser

We felt that shipping a new major without any major user-facing changes doesn’t make any sense. Since the updated code browser is so close to being merged, we’ll wait with tagging the 3.0 version until the new code browser has been merged into the next branch. We feel it’s worth waiting for:

New Gitorious UI sketch - syntax highlighting

The code browser in Gitorious 3 will not be asynchronous

We will change the code browser so it no longer runs asynchronously; rather it will be a Rack application running inside Gitorious. The git repository access is still done using libgit2/rugged, which gives great speed and stability gains, and we will finally get proper syntax highlighting courtesy of Pygments.

We hope to tag Gitorious 3.0 before the end of April, and will deploy it to gitorious.org as soon as it’s been tagged. It will feature:

  • Rails 3.2
  • Partial new UI
  • Significantly improved repository browser (Dolt)
  • New syntax highlighting, along with support for vast numbers of new languages
  • Readme-rendering for repositories
  • A JSON/HTTP based API, more details soon!
  • Ruby 1.9 support

Shortly after 3.0 lands we will keep working on propagating the UI upgrade to other parts of the application.

6 Comments

  1. nzit
    Posted April 2, 2013 at 4:05 pm | Permalink

    Awesome! I feel that the UI part is where Gitorious has been lagging behind competitors. It’s great to see you are bumping that dent.

  2. alex
    Posted April 7, 2013 at 2:05 pm | Permalink

    Yo guys wont change this shlty web interface? gitorious.org??

    Sux!

  3. Marius Mathiesen
    Posted April 8, 2013 at 7:33 am | Permalink

    @alex: thanks for the feedback. I’m sorry if I was unclear in the post: we *are* changing the UI in gitorious.org.

  4. Anonymous
    Posted April 8, 2013 at 11:58 am | Permalink

    I’m about to setup gitorious for the first time. It’s only a small codebase so I’m asking myself how stable Gitorious 3.0 already is. (Am I right that the “next” branch is the current development branch?)
    How much effort will it be to convert from a stable 2.2 to the new 3.0 release? Is it worth a shoot to already install the development tree?

    • Posted April 9, 2013 at 6:53 am | Permalink

      Hi there,

      I think some bugs are still being worked out, so your safest bet is probably to just go with stable 2.4.12 then migrate your data over to a fresh 3.x instance once we officially release the 3.0 branch.


Post a Comment

Required fields are marked *

*
*

Follow

Get every new post delivered to your Inbox.

Join 713 other followers

%d bloggers like this: