Re: [ jEdit-devel ] Draft of new release procedure using release branches

[Kazutoshi S. <k_s...@f2...>]

Matthieu Casanova wrote:
> The committers is not a very clear notion since any plugin developper can
> technically commit to jEdit's core itself if he don't want to respect the
> guidelines.

I see. It may be a problem. But I think the wording in the draft is fine
because it is in the jEdit core source tree, and has the title "Release
procedure of jEdit". Changing the title to "... of jEdit core" may be a
bit better.

> So to summarize, the same group of people will be allowed to commit to the
> trunk as before, then another developper of the same team will review the
> commit and merge it to the release branch.
> And all other developpers will continue to submit patches on the tracker
> isn't it ?

Right.

> Do you think it is possible to try your release process, and after a while
> maybe change it if it doesn't work as expected ?

Yes, of course. This proposal/draft also has come as such, finding the
old trunk-only procedure doesn't work as we want. Since it will be
documented in the repository, the change will be more easy and future
developers can learn from the history.
-- 
k_satoda