On 11/18/2010 12:08 PM, Maxime Thomas wrote: > Another point that has maybe already been discussed but how do we manage > components in the SVN, do we have separate tags and branches for the set of > components and each component ?
I think the SVN structure is a different topic and should be discussed in its dedicated thread. We currently have: trunk/ for cutting edge features releases/ with tags for every component release release-info/ with files telling which component versions were part of which full package release stable/ with branches from stable versions, if there was the need for bug fixes, but trunk/ already contained new feature code. > My point is to chose the easiest way to deliver things : if each package > must be done manually, it increases the probability of mistakes. > The best option is maybe to start with a simple package and then see what > happend (some feedback of people). > We can keep : > - the access to SVN > - the pear channel with identified version (like ezc) This is basically what we did before, except for the full package download. I actually don't want to give that one up, agreeing with Dericks points. Regards, Toby -- Tobias Schlitt http://schlitt.info GPG Key: 0xC462BC14 Want to hire me? Need quality assurance? http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn
