Re: Data structures in the next release
- Posted by jimcbrown (admin) Jul 31, 2014
- 1987 views
I know i get what i pay for ... but what i miss is 'Tue Gutes und rede darueber.' translate to 'Do good and tell people about it!'
Agreed. But, well, real-life and all that ... what's a person to do?
Make it public available... In a usable form ;) In form of binarys (working programs and anounce it).
Example : Maybe if someone ask for memstructs you can just point him to the download page ...
Wait... Aren't we already doing that?
I miss 'the progress in OpenEuphoria pushed to the public', i'am sure not every Euphoriaprogramer likes to install gcc and msys and hg to just have the most recent Interpreter.
You mean the eubins? Getting those back up is definitely a priority.
Not only the eubins,
Then what else?
but yes, they would be a good start (togehther with a simple changelog textfile).
The changelog will not change too much between hg commits. I'm not sure of the utility of this.
No not with each update, but a simple binary release (not even a full setup, maybe just a zip with a change log).
If it's per release ... then we are already doing this.
As example, for the main release (Eu 4.0.x) a zip file and a simple changelog.txt every 6 month. Just to keep people informed thats something going on.
This would be great.
This is not possible. There have been no new releases in the past 6 months.
Don't forget : Most people just visit a webpage in a few seconds, they do not browse hg logs or something like this, they look for downloads ...
I think including the full hg logs, or even the full changelog (the release notes) on the downloads page is not practical. They'd just be too large and take up too much space.
A short summary would probably work though. Since the downloads page is a wiki page editable by any logged in user, this means that any person with the spare time can go ahead and do this.
