On Mon, Jul 25, 2016, at 11:54 AM, Set Hallstrom wrote: > On 2016-07-24 23:17, Len Ovens wrote: > > > Ya, I haven't seen anything about packages actually being added > > removed... maybe it has been done and I missed it. I just meant that if > > the actual changes to our packages have not been made there is nothing > > to test. > > Ok, thanks for clarifying, Len. No i haven't seen anything either. In > fact no one has assigned themselves to a work item. > https://blueprints.launchpad.net/ubuntu/+spec/ubuntustudio-y-development > I guess i should have been more alert and pushy... > > I'd love to do a few but someone has to teach me. >
Get the latest seeds. Make the changes as specified in the wiki (additions, replacements or removals). Either do one bzr commit per change, or for the whole thing at once by referring to the planned changes. The upside with doing one commit per change is that you can throughly document the reason for that change in the commit log itself, removing the need to consult any other source. But, I leave that up to the commiter. Once the seeds are updated, anyone can just ping me and I can update the meta package - which is the only package of ours that is not really in a bzr branch (it's the same with all meta packages, usually). Once both the seeds and the meta are updated, our next ISO will contain the changes. -- ubuntu-studio-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
