From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-October/008926.html | 81 +++++++++++++++++++++++++++++ 1 file changed, 81 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-October/008926.html (limited to 'zarb-ml/mageia-dev/2011-October/008926.html') diff --git a/zarb-ml/mageia-dev/2011-October/008926.html b/zarb-ml/mageia-dev/2011-October/008926.html new file mode 100644 index 000000000..afdbe7da3 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-October/008926.html @@ -0,0 +1,81 @@ + + + + [Mageia-dev] drupal - changes + + + + + + + + + +

[Mageia-dev] drupal - changes

+ Maarten Vanraes + alien at rmail.be +
+ Mon Oct 17 10:40:39 CEST 2011 +

+
+ +
Op maandag 10 oktober 2011 13:25:55 schreef Oliver Burger:
+> Am Montag, 10. Oktober 2011, 13:04:01 schrieb Guillaume Rousse:
+> > Le 10/10/2011 11:55, Oliver Burger a écrit :
+> > > Rename drupal-7.x to drupal7 and name drupal-8.x drupal?
+> > > This will lead to existing drupal installations being updated to the
+> > > 8.x branch which will likely break loads of things.
+> > 
+> > What's the problem if it is documented, and non-destructive ? Also, you
+> > can wait one or two release before changing default version.
+[..]
+
+I would just like you to keep in mind that at work, we have a sort of 
+generalized approach to using which drupal version:
+
+- for new projects, start using the next version, only when the one after it 
+has been released.
+
+so, we still use drupal6, and will go to drupal7 when drupal8 is released, but 
+ONLY for newer projects.
+
+keep in mind that when a new drupal version is released, the current modules 
+_WILL_ be incompatible.
+
+Hell, afaik not all important modules have been converted for D7 yet...
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1