Aloha,
2010/8/5 Lasconic <
[hidden email]>:
> I will try to release 0.9.6.2 in the next hours.
Great - I'm out this evening, so I'll get that uploaded tomorrow.
> I have a question for you regarding ubuntu and debian. PPA are great but
> seem to limit the adoption of new version of MuseScore. Is there a way to
> include MuseScore in the Ubuntu update repository?
Ubuntu releases a new version of the distribution every six months. At
that point, the upstream versions of software packages are frozen: the
aim is that for the life of the release, the distribution has a known
and guaranteed level of stability. Because new upstream versions
introduce new features, potential regressions and bugs, changed UIs
and translatable strings, once an Ubuntu release is out, new versions
of individual packages are not accepted. The only changes accepted are
backported fixes for bugs or security holes. After the next six
months, the entire system can be upgraded to the next version, which
again has a guaranteed level of cohesion and stability.
There is a semi-official repository for new upstream versions: Ubuntu
Backports. This is not enabled by default, and it is not clear that it
is fully maintained. I would not recommend MuseScore to be included
there, because not only is it not much easier to enable Backports than
the PPA, Backports also provides updated versions of other packages,
which may or may not be desirable. I prefer the granularity afforded
by PPAs.
Naturally, for young software such as MuseScore, it is more likely
that a new upstream version will be on average more stable than less,
and so this is a strong point in favour of an altered release model.
However, I'm not sure that most software falls into this category, and
due to the limited manpower of the volunteer Ubuntu and Debian
developers, I'm not sure that a more fluid release process would be
beneficial on the whole. And, of course, whilst I am able to comment,
my views do not count for much in terms of decisions made.
> Regarding trunk, we are releasing windows nightly and soon MacOSX ones. But
> they are labelled as nightlies and they use a different application name, a
> different icons etc... and are designed to live next to a stable
> installation of MuseScore. To answer your question, I think it's better to
> hold on the prerelease on the trunk until we enter a debug phase.
Thanks. The MuseScore-on-Ubuntu situation is slightly different for
the Mac/Windows one: I maintain a number of patches to the upstream
sources, and because those sources change, the patches may or may not
apply on a particular day. Consequently, it's not really possible to
build 'nightlies' that reflect how those upstream sources would look
were they to become an official release on that day. And, consequently
to that, I don't think the value of vanilla nightlies is quite the
same.
Cheers,
--
Toby Smithe
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Locked
