update release page to include history of the releases and binaries about winflexbison HOT 5 CLOSED

Your help is very appreciated.
Honestly I have no time to do it in nearest weeks.
I have added you to the project collaborators, is that sufficient?

from winflexbison.

Yes, it is enough. I'll start with polishing the releases soon.

The other items need more thoughts put in first.
Especially:

• Do we need to have the bin directory under version control (especially when we have the binaries in the releases, soon)?
• Do we need to keep the two branches? I think moving the 2.x bison in to the main branch (adding a "new" VS/CMake entry and splitting chocolately into two directories) would be useful (there are actually minor differences in non-bison parts between those branches and it looks like you've did the changes in both (without merging the changes from master to branch).

What do you think about these two issues?

from winflexbison.

I agree. Just some notes:

1. bin folder includes non binary stuff. May be we should move it to src/ subfolders and copy to output dir during building? So output dir will have executables and all needed stuff.
2. I usually cherry-pick commits from master to bison2.7 I hope further upgrades m4 code won't break frozen bison2.7 code.

from winflexbison.

Releases considered to be finished:

• tags for all old releases I could fine code for (some are missing, I assumed the code was just locally) --> from 9 to 25
• release notes added / adjusted for all 25 releases, taken from SF README.txt + references to release notes for bison/flex when updated
• binary packages added to all releases (downloaded from https://sourceforge.net/projects/winflexbison/files/old_versions/)
• included bison/flex version in tag title (only done on the first two pages of releases)

I hope you like the result. Obviously this is only useful if releases-to-come (flex 2.6.5 is on its way) use a similar publishing.

I'll add the PDF for integrating the build rules as soon as this is done (but this is tracked with #15).

from winflexbison.

Thank you for a great work

from winflexbison.