Changes between Version 1 and Version 2 of WorkingConventions/Repositories

Timestamp:

11/01/12 16:32:21 (8 months ago)

Author:

igloo

Comment:

--

WorkingConventions/Repositories

@@ -91 +91 @@
 release commit on a different branch.
 
+=== From the GHC developer's point of view ===
+
 If you are not modifying these packages then you don't need to do
 anything special: A regular `./sync-all pull` will update the submodules
@@ -126 +128 @@
 ... TODO: git commands to be filled in ...
 }}}
+
+=== From the upstream maintainer's point of view ===
+
+Upstream maintainers don't need to do anything special. You can continue
+to use any version control system and whatever branching policy works best
+for you. However, there are two issues to be aware of:
+
+ * Sometimes we may need to make changes to old versions of libraries,
+   as we try to avoid making interface changes within GHC stable
+   branches and upstream development may have moved on since a GHC
+   stable branch was created. When this happens it is up to you whether
+   the changes are sent upstream as normal (and maintained in an upstream
+   branch), or whether they are left only in the GHC repository.
+
+ * For libraries that are shipped with GHC, we need to have releases of
+   libraries that can build with that GHC. There may be no suitable
+   existing release (most commonly due to trivial things such as library
+   dependencies needing to be changed, but sometimes due to real changes
+   in other libraries or the compiler), in which case we will request
+   that you make a suitable release or, if it is not convenient for you
+   to do so, we can make one on your behalf (in which case it will
+   normally have only the minimal changes necessary since the previous
+   release).