Hi Tres,
It is most embarrassing for me, but I learned a lot from that experience.
He accepted it, but we still have to wait for it to become approved by
the SRU team.
We didn't have a MOTU to even accept lmms to be considered, I e-mailed a
few MOTU from a list, but no one responded :(
This also means I will have someone I can directly contact to update
things for new releases.
So I wont have the issue that I had recently in Utopic where no one
looked until it was a few days prior to feature freeze.
So 1.0.3 did not make it into utopic, sadly.... it only has 1.0.2.
There were a few issues that needed to be addressed in the packaging,
mainly I had to update the changelog in a different way, and other minor
issues.
But, with Timo on our side we will have someone who can approve the
merge requests and move everything forward quickly.
It will (hopefully) no longer be so much of a "wait and see" game. He
also knows the Ubuntu requirements for packages very well, and can help
me spot
those little issues and fix them before-hand.
Overall, this is very good for Ubuntu to have Timo as a MOTU. We will
have much better LMMS versions now, as well as other Audio apps.
On 09/23/2014 07:21 AM, Tres Finocchiaro wrote:
> Great news. So he finally accepted 1.0.0, but we're on 1.0.3 and
> ready for 1.1.0 :)
>
> Glad to know someone is finally listening, this botched 1.0.0 is quite
> embarrassing.
>
> -Tres
>
> - tres.finocchi...@gmail.com <mailto:tres.finocchi...@gmail.com>
>
> On Tue, Sep 23, 2014 at 8:17 AM, Israel <israeld...@gmail.com
> <mailto:israeld...@gmail.com>> wrote:
>
> Hi Everyone, this is good news!
>
> Timo is a MOTU we can contact!!!
> Yay!! Now we have someone who we can talk to directly!
> This is REALLY good news
>
> -------- Forwarded Message --------
> Subject: Re: Another LMMS question
> Date: Tue, 23 Sep 2014 11:44:27 +0300
> From: Timo Jyrinki <timo.jyri...@canonical.com>
> <mailto:timo.jyri...@canonical.com>
> To: Israel <israeld...@gmail.com> <mailto:israeld...@gmail.com>
> CC: Jonathan Aquilina <eagles051...@gmail.com>
> <mailto:eagles051...@gmail.com>
>
>
>
> Hi Israel and Jonathan,
>
> After Developer Membership meeting yesterday I received my own MOTU
> rights (rights to upload to community maintained Ubuntu repositories).
>
> I've now uploaded the lmms 1.0.0 (real 1.0.0, with those two
> backported patches to fix crashes etc) to 14.04 LTS stable release
> updates queue. I fixed the changelog to be a bit more verbose and
> synced a few small bits so that they matched the original upstream
> tarball (just README and stuff were not completely as they were in the
> upstream release).
>
> It's so sad there were no MOTU:s available for the upload earlier :(
> Ubuntu Studio would badly need new people to join the project. I just
> wanted to finish this off now that I finally was able to do so. Also
> in my future Patch Pilot turns I will try to help Ubuntu Studio and
> Xubuntu when needed. Earlier it was very hard to do as I couldn't
> upload anything anyway.
>
> The SRU process itself is not too rapid, so I'll explain how it goes from
> here:
> 1. The lmms now sits at the "unapproved" queue for 14.04 LTS updates:
> https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text=
> 2. A stable release update team member needs to approve it from there.
> It should happen eventually, since as explained the current version
> has commits from non-stable branch.
> 3. Then it goes to -proposed updates - this is the next big milestone.
> The bug will be updated with instructions on verifying that the SRU is
> indeed good.
> 4. After 7 days in the -proposed updates, if the bug is tagged
> verified-done, it will move to updates and everyone on the planet will
> receive the update.
>
> The biggest hard to estimate delay is now the acceptance from the
> unapproved queue to the proposed updates. After that it will be all
> clear in 7 days.
>
> Thanks for your patience, and I hope you are able to explain the
> unfortunate length of this problem to all the lmms friends! I did see
> a lot of grumpy people around, as people tend to expect things like
> distro updates to just work. Ubuntu is largely purely community
> project, despite the perception, so like any it only works when
> volunteers work on it. Canonical only maintains the main Ubuntu
> project (desktop/server/cloud/mobile) and the few apps in 'main'
> repository, most of the 'universe' repository is purely in community
> hands (this is a bit non-straight now as some of the phone/tablet is
> in universe because of time constraints).
>
> -Timo
>
>
> On Thu, Aug 7, 2014 at 1:57 PM, Timo Jyrinki <timo.jyri...@canonical.com>
> <mailto:timo.jyri...@canonical.com> wrote:
> > Hi Israel (and Jonathan who e-mailed me separately),
> >
> > Sorry, I was again on vacations. lmms 14.04 LTS update is still
> > depending on someone with upload rights, including any MOTU (universe
> > package managers), to sponsor it from
> > http://reqorts.qa.ubuntu.com/reports/sponsoring/
> >
> > Maybe some are skipping it since they're not familiar with it, or
> > because fewer people are doing SRU:s. Also it's a community supported
> > package so Canonical people (busy with getting a phone for sale on the
> > market) with upload rights are also not possibly looking at it as a
> > priority, or many are probably don't have time to look at the queue at
> > all.
> >
> > There was a Ubuntu Studio developer who applied for upload rights
> > recently but I believe it was only for a subset of packages? If you
> > are friends with anyone from https://launchpad.net/~motu/+members
> <https://launchpad.net/%7Emotu/+members> ,
> > maybe you could get them to upload? It would be as simple as:
> >
> > sudo apt-get install bzr-builddeb
> > bzr branch lp:~israeldahl/ubuntu/trusty/lmms/lmms_1.0.0+stable
> > cd lmms_1.0.0+stable
> > bzr bd -S
> > dput ../*.changes
> >
> > Assumptions: they trust my word on the branch review
> >
> https://code.launchpad.net/~israeldahl/ubuntu/trusty/lmms/lmms_1.0.0+stable/+merge/225778
>
> <https://code.launchpad.net/%7Eisraeldahl/ubuntu/trusty/lmms/lmms_1.0.0+stable/+merge/225778>
> > that it's ok enough, and they have environment set up to do GPG signed
> > uploads etc.
> >
> > For things working better in the future, we would really need more (or
> > even a) Ubuntu Studio people to work on becoming MOTU so that the
> > multimedia parts could be better served.
> >
> > -Timo, sadly not a MOTU either
> >
> > On Mon, Jul 21, 2014 at 3:13 PM, Israel <israeld...@gmail.com>
> <mailto:israeld...@gmail.com> wrote:
> >> Hi Timo,
> >> Do you know of anyone I can contact to help get this change sponsored?
> >> I would like to move this forward if possible. I know you are busy,
> >> (and so am I) but
> >> I would really like to fix my mistake as soon as possible. I would
> like
> >> this to happen before
> >> 14.04.2 actually I'd like it to happen today if I could. I know this
> >> stuff takes a lot of time, and the SRU people are very VERY busy. And
> >> quality is an earmark of Ubuntu, which is why I think this change is
> >> very important.
> >>
> >> Again, thank you so much for all your help! I have been working on my
> >> own project so I have been learning a lot more about what a program
> >> needs to be packaged, and how it all works together, so I am glad that
> >> this is much easier than it was back around 0.4.13 :)
> >>
> >> Thanks!!
> >>
> >> --
> >> Regards
> >>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
> Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> LMMS-devel mailing list
> LMMS-devel@lists.sourceforge.net
> <mailto:LMMS-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/lmms-devel
>
>
--
Regards
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
