| Chrislejohn | Hello world | 00:42 |
|---|---|---|
| dmj | Woot! The Ubuntu App submission process is quite painless. | 02:34 |
| pavolzetor | hi | 14:03 |
| pavolzetor | how can I make 2 branches in one project? | 14:04 |
| pavolzetor | I would like to have | 14:04 |
| pavolzetor | floaty/service | 14:04 |
| pavolzetor | floaty/client | 14:04 |
| pavolzetor | or do I need to have it as | 14:04 |
| pavolzetor | floaty-service | 14:04 |
| pavolzetor | and floaty-client? | 14:04 |
| pavolzetor | thans | 14:04 |
| pavolzetor | tanks | 14:04 |
| pavolzetor | but in project page | 14:07 |
| pavolzetor | you can have only one branch | 14:07 |
| commandoline | pavolzetor: do you just want to separate code, or also bugs, blueprints etc.? | 14:08 |
| pavolzetor | just code | 14:09 |
| pavolzetor | to have 2 separate logs of changes | 14:09 |
| pavolzetor | bugs can be in mixed | 14:09 |
| pavolzetor | I will package it also separated | 14:09 |
| commandoline | well, packaging is separate from this :) | 14:10 |
| pavolzetor | I see | 14:10 |
| pavolzetor | but I think it could be sueful to have 2 logs | 14:10 |
| commandoline | then you can just push your code to two different locations, e.g.: | 14:10 |
| commandoline | lp:~branchowner/projectname/client | 14:10 |
| commandoline | and | 14:10 |
| pavolzetor | gonig to toilet, be rgiht back :) | 14:10 |
| commandoline | lp:~branchowner/projectname/service | 14:10 |
| commandoline | the disadvantage of that is that you can only link one branch to a series, but that's the closest to what you want if you register one project. | 14:11 |
| pavolzetor | okay | 14:17 |
| pavolzetor | back | 14:17 |
| pavolzetor | sorry | 14:17 |
| pavolzetor | hmm | 14:18 |
| pavolzetor | but with this approach I cannot have releases right? | 14:18 |
| pavolzetor | like | 14:18 |
| pavolzetor | 0.1 branch | 14:18 |
| pavolzetor | 0.2 | 14:18 |
| pavolzetor | and so on | 14:18 |
| pavolzetor | Series | 14:18 |
| commandoline | well, you can register multiple series of course. One for the client, one for the service. | 14:19 |
| commandoline | But that's not really where they're meant for | 14:19 |
| commandoline | registering two projects might be the better solution here, I think. | 14:20 |
| pavolzetor | I see | 14:23 |
| pavolzetor | so when I will register 2 projects | 14:23 |
| pavolzetor | can I have one PPA for them? | 14:23 |
| commandoline | PPA's are associated to a team or person, as far as I know. | 14:24 |
| pavolzetor | hmm | 14:24 |
| commandoline | you can use one team for multiple projects, that's no problem. I do that myself for a few projects... | 14:24 |
| pavolzetor | Thanks | 14:24 |
| commandoline | so then you can also share the PPA | 14:24 |
| commandoline | you're welcome :) | 14:25 |
| pavolzetor | I just think, if it is okay to have 2 projects | 14:25 |
| pavolzetor | you know | 14:25 |
| pavolzetor | I mean it will be harder to manage | 14:25 |
| pavolzetor | eveything twice :) | 14:25 |
| pavolzetor | okay I am going to make 2 projects | 14:27 |
| pavolzetor | it is quite hard to start with development | 14:29 |
| commandoline | Two projects is a bit harder to set up, but as soon as it's all running it's not that much extra work anymore. | 14:32 |
| pavolzetor | https://launchpad.net/floaty-service | 14:34 |
| pavolzetor | https://launchpad.net/floaty | 14:34 |
| pavolzetor | is this okay? | 14:34 |
| commandoline | yep, looks ok to me :) | 14:37 |
| pavolzetor | I am going to read what file structure should be an packaging | 14:37 |
| === Guest41985 is now known as jalcine | ||
| === jalcine is now known as jalcine_ | ||
| === jalcine_ is now known as Guest972 | ||
| === webjadmin_ is now known as Guest8360 | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!