CVS access policy, branching/tagging, code review, etc.

[Kaleb S. KEITHLEY]

Keith Packard wrote:
> Around 14 o'clock on Mar 2, Egbert Eich wrote:
> 
> 
>>For releases there should be a release branch. This should be off
>>limit for everyone except the people who are involved in the release
>>process.
> 
> 
> Hmm.  I'd rather see the release done on HEAD; otherwise, there's work to 
> be done to make HEAD current after the release, which seems error prone.
> 
> That presumes that most commits during a release process will be focused 
> on the release, which seems sensible for me, but may not be right for 
> everyone.
> 
> Perhaps a 'shared' branch could be formed for people who want to ignore 
> the release and just keep working?

Yes, the shared branch is called (XORG)-CURRENT.

--

Kaleb