Foresight 20/20 Recap: Development Process

One of the first sessions on Saturday was a discussion on defining the development process for Foresight. (Unfortunately this was a session I missed, but it sounded fairly technical anyway!)

Most developers have been committing packages to the 2-devel label (rather than :devel) and the decision was made to stick to 2-devel. Additionally, one big change is the concept of creating a new repository outside of Foresight for true development and big changes that are tested in this sandbox beore moving to fl:2-devel. In my opinion, this is a great idea, as it’s fairly easy for users to install packages from the 2-devel label. (Epiphany is a great example – right now in 2-devel it’s based on Webkit – a few users have encountered errors based on the Webkit dependencies needed). This should make it better for users, as the chance to break their desktop will diminish.

Labels for these new sandboxes will be based on the JIRA issues that define what the work being done is.

For more details, see the JIRA issue discussing the new development process.

Related

comments powered by Disqus