pkeus wrote:I'll tag beta2 tonight (with no-whitespace tag like R0.6-beta2 (R for Release)) and build source packages
Suggestion: Continue the style I used for first beta ("0.6 Beta 1"). I know, this style hasn't been discussed in public, so if it causes any problems, feel free to use another one. "R" prefix is useless imho, since everything in /tags is (per definition) a release.
Whitespaces can be slight annoyance, so I'd rather at least avoid them. Is "0.6-Beta-2" ok? The R -prefix is just something I'm used to in some other projects, but I agree with you that it's redundant (there's slight benefit if one takes svn checkouts from branch and tag without giving names for the local dirs, they would end distinct as "S0.6" and "R0.6")
pkeus wrote:2. You'll build windows binaries, from source packages, not svn (so the source packages get tested too), and do some basic testing with them
Yes. Will you put the package to sourceforge downloads?
Yes. I'll add it there somehow. Before RCs we should design sourceforge downloads hierarchy too - automatic watch -files and the like should be able to easily find the new versions etc.
pkeus wrote:4. If there's nothing we want to immediately (before branching) fix, I'll branch S0.6 (Stable) during the weekend
I prefer to branch immediately after tagging, since I've got some changes in the pipeline I would like to commit soon. If you agree, I can create the branch as soon as I start to commit my changes into trunk (after you tagged Beta 2). Would probably happen tomorrow then.
Ok, if you already have trunk-only stuff waiting, we can branch immediately (could even branch first and create the beta2 from the branch) What we should call the branch then, or is "S0.6" ok for a branch name?
In trunk I'll move source files to their own subdirectory. I'll fix autotools side, but paths in windows build files are left to you. We need to freeze trunk while I do this as any commit to wrong path certainly conflicts. That's probably something I'll do Saturday-Sunday night, but I'll post confirmation here about an hour before.
Again, if you have stuff ready to go in with current paths, it's easier to get those in first.