Uds

Ubuntu Make 16.01.2 with Swift, eclipse php and eclipse cpp support

Last week, during UbuCon Summit, I had the pleasure to announce in sunny Pasadena a new Ubuntu Make release! Marking the 16.01.2 milestone, this one provides thanks to community contributions 3 new supported frameworks. The first one is the new Apple's opensource language name Swift lang. A lot of people are becoming more and more excited about it, and now, getting it running on Ubuntu is just a umake swift away!

Ubuntu Developer Tools needs you for its new name!

We’ve been talking about the Ubuntu Developer Tools Center for a few months now. We’ve seen a lot of people testing it out & contributing and we had a good session at the Ubuntu Online Summit about what the near future holds for UDTC. Also during that session, emerging from feedback we received we talked about how “UDTC” and “Ubuntu Developer Tools Centre” is a bit of mouthfull, and the acronym is quite easy to muddle.

Eclipse and android adt support now in Ubuntu Developer Tools Center

Eclipse and Android ADT support now in Ubuntu Developer Tools Center Now that the excellent Ubuntu 14.10 is released, it's time to focus as part of our Ubuntu Loves Developers effort on the Ubuntu Developer Tools Center and cutting a new release, bringing numerous new exciting features and framework support! 0.1 Release main features Eclipse support Eclipse is now part of the Ubuntu Developer Tools Center thanks to the excellent work of Tin Tvrtković who implemented the needed bits to bring that up to our users!

Ubuntu Developer Summit: résumé et discussion avec la communauté francophone. En direct, ce soir, 21h (heure française)

Bonjour à tous, Suite à une discussion lors de la dernière Ubuntu Party à Paris, une proposition a été faite de résumer ce qui a été débattu pendant l'Ubuntu Developer Summit en ligne qui a eu lieu de mardi à jeudi soir. Pour rappelle l'UDS est le lieu (maintenant complètement en ligne) où toutes les décisions techniques concernant le développement d'Ubuntu sont prises. Tout le monde est invité à participer par conférence vidéo ou directement sur IRC.

Followup UDS session on application lifecycle

I hope that everyone enjoyed the new virtual UDS format as we did. :) However, don't despair, it's not really *over* yet! The discussion around the application lifecycle[1] was covering a too large spectrum and we didn't get time to properly finish discussing it. As we didn't want to run over other sessions, we decided to reschedule it just after UDS. The new follow-up session "Application model: lifecycle" will happen this Friday, March 8, 16:00 – 16:25 UTC.

Unity: release early, release often… release daily! (part 5 and conclusion)

This post is part of the Unity daily release process blog post suite. After a week to let people ask questions about the daily release process, I guess it's time to catch up and conclude this serie with a FAQ and some thoughts for the future. FAQ The FAQ is divided in multiple sequences depending on your role in the development of ubuntu, with the hope that you will be able to find what you are looking for quicker this way.

Unity: release early, release often… release daily! (part 4)

This post is part of the Unity daily release process blog post suite. You hopefully recovered from your migraine on reading yesterday's blog post on the insight of daily release and are hungry for more. What's? That's not it? Well, mostly, but we purposely dismissed one of the biggest point and consequences on having stacks: they depends on each other! Illustrating the problem Let's say that Mr T. has an awesome patch for the indicator stack, but this one needs as well some changes in Unity and is not retro-compatible.

Unity: release early, release often… release daily! (part 3)

This post is part of the Unity daily release process blog post suite. Now that we know how branches are flying to trunk and how we ensure that the packaging metadata are in sync with our delivery, let's swing to the heart of the daily release process! Preliminary notes on daily release This workflow is heavily using other components that we rely on. In addition to our own tool for daily release, which is available here, we needed to use jenkins for scheduling, controlling and monitoring the different parts of the process.

Unity: release early, release often… release daily! (part 2)

This post is part of the Unity daily release process blog post suite. As part of the new Unity release procedure, let's first have look at the start of the story of a branch, how does it reach trunk? The merge procedure Starting the 12.04 development cycle, we needed upstream to be able to reliably and easily get their changes into trunk. To ensure that every commits in trunk pass some basic unit tests and doesn't break the build, that would obviously mean some automation would take place.

Unity: release early, release often… release daily! (part 1)

This post is part of the Unity daily release process blog post suite. This is part one, you can find: part 2 on upstream merge process part 3 on the daily release machinery part 4 on how dependencies are handled between stacks part 5 for a FAQ and conclusion For almost the past 2 weeks (and some months for other part of the stacks), we have automated daily release of most of the Unity components directly delivered to Ubuntu raring.