=== shadeslayer is now known as shaderslayer
=== keithjarret is now known as garr
[14:37] <grepper> wgrant: I repacked the debian/ubuntu to use the python3 ready 'txt2tags' script from the python3 branch of txt2tags. (more or less as you suggested). Where would be a good place to upload it to? Current ppa is called 'tovid-ppa' at https://launchpad.net/~grepper/+archive/ubuntu/ppa. Do I just create a branch for it within that ppa?
[21:49] <wgrant> grepper: I don't understand what you mean by "branch for it within that ppa". You can just upload the package to that PPA, no need for a branch.
[21:51] <grepper> wgrant: okay, I just thought it was strange to have a 'txt2tags' in a ppa named 'tovid-ppa'
[21:51] <wgrant> grepper: Shrug, it's a dependency, seems reasonable to me.
[21:52] <grepper> maybe I have been using branches wrongly, too much svn background I guess - I created a 0.35.2 branch when I updated from 0.35.1 which was dumb I guess ?
[21:53] <wgrant> grepper: What do you mean by "created a 0.35.2 branch"?
[21:54] <wgrant> What kind of branch?
[21:55] <grepper> for uploading code
[21:56] <grepper> https://code.launchpad.net/~grepper
[21:56] <wgrant> Ah, so you mean an actual Bazaar branch, right.
[21:57] <grepper> yes
[21:57] <wgrant> Using branches that way isn't by any means wrong, but it's unusual.
[21:57] <wgrant> It would be more common to have eg. a 0.35 branch which gets updated with 0.35.1, 0.35.2, etc.
[21:57] <wgrant> Since a branch with 0.35.1 in the name is probably always going to be 0.35.1, which makes it sorta pointless.
[21:57] <grepper> you mean using tags ?
[21:58] <grepper> ie. to be able to go back and check out older code
[21:58] <wgrant> Right, it's common to use tags to specify which revision corresponds to which package version.
[21:58] <wgrant> Tools like debcommit will automatically add them for you.
[21:58] <grepper> okay, thanks
[21:59] <wgrant> If you look at Ubuntu's official branches, we have one for each package for each series.
[21:59] <wgrant> eg. there's the dpkg trusty branch, the dpkg vivid branch, etc.
[21:59] <grepper> guess I'm royally confused after just moving my project from google code to githup (svn -> git) and now bzr
[22:00] <grepper> I have it backwards I guess
[22:00] <grepper> as all dists are in  each branch
[22:00] <wgrant> In terms of how you use them to manage releases, branches in all three VCSes are reasonably similar.
[22:00] <grepper> not that it really matters as its exactly the same code
[22:00] <wgrant> Right, you probably don't want to operate quite like Ubuntu.
[22:00] <grepper> okay, thanks for your clarification
[22:01] <wgrant> Ubuntu doesn't push the same release to everywhere -- we don't push 2.0 to trusty if trusty had 1.0 originally.
[22:01] <wgrant> So we need separate branches so we can backport fixes to any version in a stable release.
[22:01] <wgrant> In your case, you probably have a single branch that builds on all series.
[22:01] <grepper> right
[22:01] <wgrant> It might make sense to just have a "tovid-ppa" branch, for example.
[22:02] <grepper> maybe I'll tag then merge them, if I can figure out how ...