Yes Sergey I fully agreed that we should split contracts into their own project(s) and package(s). In this way, we could have their package depend on the app they relate to. Really the proper thing to do is ship contracts *with* apps, but if we can't do that this is probably the next best thing.
Best Regards, Daniel Foré El may 23, 2012, a las 9:37 a.m., "Sergey \"Shnatsel\" Davidoff" <ser...@elementaryos.org> escribió: > Contractor didn't follow the milestone scheme either (maybe this is why it > looked so unattended...). Anyway, I've fixed it: > https://launchpad.net/contractor/+milestone/luna-beta1 > > The milestone has 2 code-related bugs, 1 crash (BOO!!) and 1 bug in a > contract shipped with it. I keep wondering if I should split those contracts > out the core and make a separate package+lp_project for them... > > If nobody replies to this mail, I'll rename > https://launchpad.net/granite/+milestone/0.1.1 to luna-beta1 to get Granite > back in the Luna loop. Of course I'd prefer the actual maintainers to take > care of the project because I'm but a script kitty and know almost nothing > about that shared library of Coders. > > -- > Sergey "Shnatsel" Davidoff > OS integrator @ elementary > > -- > Mailing list: https://launchpad.net/~elementary-dev-community > Post to : elementary-dev-community@lists.launchpad.net > Unsubscribe : https://launchpad.net/~elementary-dev-community > More help : https://help.launchpad.net/ListHelp
-- Mailing list: https://launchpad.net/~elementary-dev-community Post to : elementary-dev-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~elementary-dev-community More help : https://help.launchpad.net/ListHelp
