AVKuznetsov wrote:
In any case that are details. The main must be adopted by active developers and by Scott as the project admin.
OK. I just made a branch tag for BETA_5_6 right at the top of the mainline. The name is purely for parity with old releases, you don't need to beta if you don't want. We can even release off the branch, that's OK.
If you want to fool around and do some more experimental changes: stay on the mainline.
If you want to make stability changes for 5.6 only: do cvs update -r BETA_5_6 and commit there. If there are no changes needed, then the branch will just be a no-op.
I will hand the keys to file-release to anyone who volunteers it. You get that means you get to clean up the release notes, package up the source, etc. It's up to you if you want to do a source-only release.
Sorry I don't have time to do all the drudge work these days, but I can make it easier for others.
-- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
