#musicbrainz-devel

/

      • kepstin joined the channel
      • hawke_1 joined the channel
      • kurtjx joined the channel
      • kurtjx joined the channel
      • noobie joined the channel
      • kurtjx joined the channel
      • kurtjx joined the channel
      • kurtjx joined the channel
      • kurtjx joined the channel
      • SexyKen-FN
        Hm.
      • SexyKen-FN has left the channel
      • SexyKen joined the channel
      • SexyKen
        Anyone here?
      • ruaok
        no
      • :-)
      • ijabz joined the channel
      • outsidecontext joined the channel
      • warp
        :)
      • ijabz joined the channel
      • outsidecontext joined the channel
      • reosarevok joined the channel
      • ijabz joined the channel
      • ruaok_ joined the channel
      • djce joined the channel
      • reosarevok joined the channel
      • plaintext joined the channel
      • adhawkins joined the channel
      • adhawkins
        Just out of interest, is there a release date set for CAA?
      • warp
        not afaik.
      • adhawkins
        Ok cool.
      • Wondering when I should consider getting Debian packaging for libcoverart underway.
      • warp
        with enough time to make it into the next stable release :)
      • adhawkins
        Oh ok, plenty of time then.
      • Next stable release freezes in mid-June, so we've almost certainly missed that.
      • outsidecontext_ joined the channel
      • warp
        really?
      • adhawkins
        I imagine so, we haven't officially released libcoverart yet. No point trying to package a Beta up for Debian.
      • Plan was to officially release libcoverart when CAA is announced.
      • warp
        I mean, the freeze in june. I am subscribed to debian-devel-announce, where I assume such stuff would be posted to.
      • adhawkins
        I have seen it somewhere, one sec
      • warp
        ah, it was announced on debian-devel-announce around the time of my flight back to .nl
      • adhawkins
      • ruaok
        CAA will be annonced on Oct 9.
      • announced even.
      • adhawkins
        Ok, that gives me an idea of when to schedule things.
      • Hopefully we can get libcoverart into Debian without the last minute rush that happened with libmb4/5
      • Something else that occurred to me. If libmb5 ever gets to v5.0.9, what should the next release number be if it is only minor bug fixes?
      • Is 5.0.10 acceptable generally? (we do that here at work)
      • warp
        adhawkins: acceptable to who? it certainly is acceptable to me :)
      • adhawkins
        Just wondered if there was a generally accepted scheme for this.
      • If it were just major.minor, 5.1 and 5.10 are numerically identical
      • warp
        adhawkins: there are a few different standards which you can choose to follow if you want.
      • adhawkins reads
      • there may be more.
      • adhawkins
        Erk, we've already 'broken' semver
      • "Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. "
      • warp
        :)
      • adhawkins
        However, point 12 effectively says all number between the '.' are considered independantly. Major first, then minor, then patch.
      • warp
        I wouldn't consider 5.1 and 5.10 to be identical when used as software versions.
      • adhawkins
        Ok.
      • Sounds like in future 'schema' changes should cause a minor version bump, not a patch version as I've been doing.
      • That might complicate packaging some more :)
      • warp
        adhawkins: if you choose to follow semver. you also make your own statement about what all of it means.
      • +can
      • adhawkins
        Yeah.
      • warp
        but I guess following semver would be appreciated by some groups of packagers and users.
      • adhawkins
        But the apache one is similar. Patch level versions are for pure bug fixes only. New functionality should increase minor version.
      • warp nods.
      • I'll have to see how that affects things like Debian.
      • For example would libmb5 and libmb5.1 be different packages, or still called libmb5?
      • warp
        I have no idea. I know very little about debian packaging.
      • adhawkins
        Ok.
      • teuf
        adhawkins: still libmb5 unless you break api/abi and want those to be parallel-installable
      • (which you don't want)
      • reosarevok
        "Google scores victory: judge rules APIs not copyrightable"
      • Guess that's good news, since less legal BS tends to be
      • adhawkins
        teuf: I think I agree there.
      • warp
        reosarevok: yes, that definitely is good (though not unexpected) news.
      • reosarevok: I was more worried about the patent phase, but google won that as well.
      • teuf
        adhawkins: using the 2nd number to tag schema changes, and the last one for bug fixes would be nice
      • adhawkins: but anything will do imo
      • adhawkins
        Yes, that's what I think we'll do moving forward.
      • Just trying to work out how that fits into Debian etc.
      • warp
        reosarevok: so I think the oracle vs. google case is now over (apart from some formalities).
      • teuf
        adhawkins: don't worry too much about that ;)
      • adhawkins
        teuf: Well, Debian is what I use so it'd be nice to handle it properly!
      • warp
        I still use Debian on two machines. but the slow release cycle is now starting to annoy me, so I'm considering switching everything over to Ubuntu.
      • adhawkins
        My main server is debian (firewall, routing, DNS, NTTP, SMTP, POP3 etc). I like the fact that I know it's just going to keep working.
      • I don't really need new versions mostly.
      • warp
        adhawkins: development cycles have speed up in recent years.
      • adhawkins
        Yeah
      • warp
        as a webdeveloper doing javascript it is convenient that I can just 'sudo apt-get install nodejs' on ubuntu to get a working javascript prompt
      • (even though I don't care about node.js as a platform)
      • stuff like that being available faster is making ubuntu quite tempting, even on servers.
      • teuf
        adhawkins: what I mean is that debian doesn't really care about how you version your module
      • adhawkins
        Yeah, just been asking that on a debian channel, and as long as the SONAME stays the same, the package name should too.
      • So in future, if there's new functionality (schema changes and hte like) the minor version will get bumped. Pure bug fixes will just increment the patch version
      • doskir joined the channel
      • marco-oliveira
        hi everyone
      • doskir_ joined the channel
      • outsidecontext joined the channel
      • warp
        bitmap: boo!
      • bitmap: how are you doing with your gsoc stuff?
      • ijabz joined the channel
      • plaintext
        I wrote the log sanitizing script
      • Does anybody want to see?
      • kurtjx joined the channel
      • gravelld joined the channel
      • ijabz joined the channel
      • gravelld
        Has anyone been working on a semi-automated bot for uploading artwork to CAA? I heard a rumour there was one in the works.
      • reosarevok
        Rumours, all!
      • ijabz joined the channel
      • gravelld
        Righto
      • Thanks Reo
      • I'll go git my lunch
      • Ooops I mean get
      • reosarevok
        :D
      • kepstin-work wishes he could use git to pull lunches.
      • gravelld is still trying to work out how to incorporate 'fork' into the puntastic convo
      • kepstin-work
        fork... lunch... ? It should be trivial.
      • but yeah, the awesome thing about gitting someone else's lunch then by forking it is that they still have their lunch :)
      • got to love digital non-scarcity.
      • plaintext_ joined the channel
      • so, is it intentional that people aren't allowed to log in to classic.musicbrainz.org?
      • I wanted to look at the pre-ngs-conversion edit history for something for comparison purposes
      • but I couldn't, since login is disabled.
      • kurtjx joined the channel
      • kepstin-work welcomes navap to the canadian english translation team :)
      • marcooliveira joined the channel
      • ijabz joined the channel
      • ijabz joined the channel
      • hawke_1 joined the channel
      • bitmap
        warp: so far so good, though I realized the javascript is a bit annoying because it involves template-y stuff that jquery doesn't do well on its own (i.e. adding/removing/changing relationships and then updating the UI)
      • if I could I would use something like http://knockoutjs.com/ but I realize that's departing a lot from the rest of the MB js
      • kepstin-work
        me uses json-template on http://people.scs.carleton.ca/~cwalton3/temp/mb... - it's kind of a neat javascript template library, that doesn't pull in any junk :)
      • voiceinsideyou
        luks: thanks for furiously merging my trivial Picard patches :D
      • (and bitmap too)
      • bitmap
        mostly luks :)
      • ruaok joined the channel
      • warp
        bitmap: ah, don't know knockout
      • bitmap
        I used it in a previous project and it's pretty awesome
      • warp
        bitmap: ocharles and I have discussed templating before. I would really like a solution where we can use templates on both client and server.
      • bitmap
        that'd be nice, since relationship_editor.tt needs the same template as the js to display the initial relationships
      • the_metalgamer joined the channel
      • warp
        bitmap: I would be inclined to render that with javascript as well, especially if server and client-side do not share templates.
      • bitmap
        warp: at first I was thinking about encoding all of the relationships as json into the js, and have it render them