On Wed, 2002-11-27 at 12:50, Erich Titl wrote: > Mike Noyes wrote the following at 17:28 25.11.2002: > >The bering-uclibc team is making good use of our cvs repository. We now > >have two release/branch source trees under construction in cvs. > > > >Other LEAF release/branch lead developers please take note of these > >source trees. I'd like to see more of this. > > Looks like the uclibc is quite a homogeneous group, so they could agree on > the model. Or maybe the lead there just decided to go that way.
Erich, How project members reach decisions internal to a team is up to the lead developer. You would have to ask K.P. how the bering-uclibc team decided on a structure for its source tree. Since David is the only team member for Oxygen, he created its structure. > With the > consent of the lead developers of each branch it should be possible to > build a tree which does not necessarily have to be maintained by the lead > developer. I don't think so. By definition a lead developer is in charge of the release/branch purpose and direction. Aren't both lost when abdicating source tree control? I believe a release/branch source tree in our repository not endorsed by it's lead developer would be a new release/branch? > But without his consent to allod/include modifications to the > tree such a venture is near to pointless. Agreed. > Maybe we could invite the lead developers of the various branches to mirror > their respective cvs tree(s) to a public place where it is possible for the > other developers to make branches/modifications which eventually would be > either rejected or make it to the base. Of course this might change the > development cycle a little. I'd like to avoid numerous cvs branch creations in our repository. Merging multiple cvs branches is a significant challenge. Currently, there are three preferred ways to handle patches. One, they can be submitted in our SF patch manager. Two, the person with the patch can be added to the release/branch team, and given write access to the team source tree in cvs. Three, provided the person is a LEAF project member, the patch can be committed to their personal tree in our cvs repository. The least desirable method is direct submission to a lead developer, as there is no way to track the submission. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
