Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The problem with your problem is that your library is not a library, at least not in a strict sense of the expression.</p> <p>Your "library" is better described as a project that happens to be shared by the teams working on the different applications that rely on that core.</p> <p>In this context, the biggest issue is not the subversion technique you may choose to use, but the way you organize your team in order to achieve a useful collaboration on that core component.</p> <p>And the kind of problems that may arise are at least two. First, as the different applications may need different behaviors from your core, if they do not coordinate well, a perfectly valid commit from one team will break the other ones (continuous integration should help here).</p> <p>But the second problem is harder to solve even with good inter-team communication, and it's related to the release management.</p> <p>If the applications depending on this core are released at different points in time, you will have a hard time getting a stable core that is good enough for the release of one the apps while not halting the development of the rest.</p> <p>My suggestion, have somebody dedicated to look after the core library. Use a branch of it in every project and let the applications developers to commit there while ensuring that they discuss the changes with everybody, specially the overseer of the lib.</p> <p>And finally, make this library supervisor be in charge of coordinating the merges of the changes made by the different teams into the trunk of the library, thus generating stable, tested releases that will be used by the stable releases of your applications. And after every release of the core, spawn the next generation of branches into the rest of the projects.</p> <p>It sounds like a lot of work compared with just defining an external and let everybody commit there. But actually, there is no point in hiding the fact that you must put some effort in keeping your core library coherent. If you don't do it upfront it will hunt you later.</p>
    singulars
    1. This table or related slice is empty.
    1. POMaking SVN's externals definitions fool-proof?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJavier
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou are right with the lib not really being a lib, but it was somewhat easier to explain (plus it doesn't really make a difference).
      singulars
      1. PO
      1. USSteven
    2. COYeah, I guess it is much easier to explain it that way. And I know it's a matter of semantics, but I think of libraries as more or less static artifacts, which is not the case here because the "lib" is in development state. Otherwise vendor branches would do.
      singulars
      1. PO
      1. USJavier
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload