[development] tagadelic 'backport' for 4.7

Bèr Kessels ber at webschuur.com
Tue Oct 3 13:54:41 UTC 2006


I am receiving the first patches to make tagadelic ready for 5. However, till 
today, I managed to keep tagadelic HEAD running very fine on 4.7. It got 
loads of nice features, improved code, and revised, more modular APIs. 
branch 4.7 tagadelic, and HEAD tagadelic are not compatible, so if I simply 
overwrite the 4.7 branch with tagadelic HEAD I will break a lot of people's 

Hence I want to roll out a 4.7-2 soon, and then focus on 5.0.

 * Drupal does not allow me to create separate 4.7. Should i therefore use my 
own SVN to distribute that new version?
 * Does anyone (bryght, Civicspace, etc) have an infrastructure in lpace to 
distribute backported modules and features, which is could use instead of 
roling my own (see above).
  * What is the status of allowing 4.7.2 branches for modules? Should I rather 
wait for that?

| Bèr Kessels | webschuur.com | Drupal, Joomla and Ruby on Rails web 
development |
| Jabber & Google Talk: ber at jabber.webschuur.com |
| http://bler.webschuur.com | http://www.webschuur.com |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://lists.drupal.org/pipermail/development/attachments/20061003/5456653e/attachment.pgp

More information about the development mailing list