yade-dev team mailing list archive

[Anton Gladky <gladky.anton@xxxxxxxxx>]

Hi, all,

I decided to start a new thread, answering on Sergei's email.
I completely agree with him about controlling any commits. Fighting
with bugs is really difficult and long-time work, and we should
minimize those efforts, focusing on more useful work.

I suggest:
* create a new team, something like yade-security, yade-approvers etc.
* create a branch, owned by this team.
* all commits to this new branch should be done by somebody from this team.

Yade buildbot needs to control and compile each revision, making
corresponding tests after compiling (like it is now). We should also
care about adding some more additional tests to --checks section.

All comments and discussions are very welcome.

Anton


On Fri, Mar 18, 2011 at 11:25 AM, Sergei D. <sj2001@xxxxxxxxx> wrote:
>
>> Is there anybody who will stand up and take over the leadership?
>>
> Hello All,
> If no new leader, we need some rules for commits.
> It is important if new people will join to develop.  And it is important for
> current command, because no one has so many skills as Vaclav. He did review
> all commits, so everyone can be calm, that does not disrupt Yade. So, we
> need a review's system for commits (as for articles, for example). Each
> commit should be approved by one (or two) from command. Main trunk will have
> only approved commits. Dev trunk will have commits for approve. Merging a
> main with a dev should be done by other from command, not one who did a
> commit.
> What do all think about this?
>
> --
> Best regards,
> Sergei D.
>