> Ac is stable release for which we have appropriate branch and Th > is in constant development mode, isn't it?
This is one area where PLD's release system is actually pretty wonky. Other than a few emebeded or very static applications, AC is simply too old to use for most stable systems. This puts the pressure on TH -- as in reality, most folks use PLD for it's rolling constant development branch. Anything that breaks that breaks production systems. > I am asking because I am bit lost with above arguments - do we > have some new rules for Th? When they changed? :P As far as I know, nothing has changed. This has been my understanding of the status quo since I started using PLD nearly a decade ago. > To repeat myself "cvs head != Th ftp". If you send it to the builders, > then it is your fault. I understand the difference beteween HEAD and FTP servers. The thing is, by introducing unstable packages to HEAD, you make life complicated for some of us. I for one compile a lot of software using builder from CVS HEAD. Sometimes if there are holdups on TH, stuff will actually be ahead of TH in my personal repos. When something gets introduced to HEAD that is a complete mis-match with what is currently in TH, it makes building software harder. Let's turn this question around. Since you're the one asking to do something non-standard, what is your rational? What do you gain by putting an RC version in HEAD? If you are compiling it anyway, why can't you just use the DEVEL tag until the package goes stable and people should start testing it to go into TH? Caleb _______________________________________________ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en