Hi Max, We are doing this because we are getting rid of the app-based teams. The current projects subdivision is related to our team structure. The Soyuz team monitors the Soyuz project, the Bugs team monitors the Bugs project, etc. The fact that the Blueprint and Answers projects were not monitored was the result of the fact that there were no teams responsible for them.
Starting Feb 17th, there won't be any Soyuz or Bugs or Code or whatever team anymore. All bugs will be the responsibility of all developers. We are in transition to this new structure and the merging of the old team-based projects is a step in that transition. Launchpad will track its bugs like any other projects on Launchpad. We'll use tag to associate bugs to components. These components are going to be finer grained then the old team-based componentization. -- Francis J. Lacoste [email protected] On December 14, 2010, Max Bowsher wrote: > On 14/12/10 15:53, Francis J. Lacoste wrote: > > On December 13, 2010, Max Bowsher wrote: > >> Including a "The new way to search bugs just within the Soyuz component > >> of Launchpad is ..." (etc.) in the blog post would likely make it a lot > >> less likely to make people think negatively about the change. > > > > In a way, the fact that all components are part of the same project > > should help with finding duplicate. Before if you file a bug against the > > wrong project, you wouldn't find the existing bug whereas now it won't > > be a problem. > > > > There is no real way anymore to search only the Soyuz component, since > > there isn't such a thing as a 'Soyuz' component. It's really an > > aggregation of multiple components (publisher, buildd-manager, plus a > > bunch of web features.) There is the 'lp-soyuz' tag, but these are > > temporary as they only reflect an arbitrary aggregation of components. > > The lumping together of all bugs across separate and generally fairly > well definable major areas of Launchpad (i.e. Bugs, Code, Soyuz, etc.) > feels negative to me. > > I'd imagine I'm not the only one. > > Therefore, I think it's very important the rationale for doing so is > clearly communicated. > > Max.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
