Posted: Sun May 05, 2013 6:22 pm Post subject:
Ares 0.3 RC phase
Hello guys,
Ares 0.3 is almost done, even though it didn't go exactly as planned. I think you all have seen the blitter crash thread by now, and the week long delay. Then, some fixes weren't confirmed as working. In the last weeks, some more issues popped up and they have been tackled. Thus the delay lead to a more stable Ares 0.3 instead of Ares 0.3 followed by a 0.3p1 patch.
Alas the Attach Effect feature didn't make it in time, but all other features like the Whiteboy fix and Custom Missiles will be in.
The included documentation is preliminary, although complete. The wording might change, but all new tags should work as described. If you got some comments, please post them here! _________________ QUICK_EDIT
Joined: 22 Nov 2010 Location: Iszkaszentgyorgy, Hungary
Posted: Sun May 05, 2013 6:44 pm Post subject:
Congratz.
On the summer I rewire my stuff for a faster 0.4 release then. If you plan to include those on your planned 0.4 feature-list. _________________ "If you didn't get angry and mad and frustrated, that means you don't care about the end result, and are doing something wrong." - Greg Kroah-Hartman
=======================
Past C&C projects: Attacque Supérior (2010-2019); Valiant Shades (2019-2021)
=======================
WeiDU mods: Random Graion Tweaks | Graion's Soundsets
Maintainance: Extra Expanded Enhanced Encounters! | BGEESpawn
Contributions: EE Fixpack | Enhanced Edition Trilogy | DSotSC (Trilogy) | UB_IWD | SotSC & a lot more... QUICK_EDIT
I shall pick up on some of the testing. I will try to find some of the new features that I can use into my mod and test them. I am not making a commitment, but I am offering to try to help.
EDIT: I would really love for the documentation to have a filter for version additions, much like one of the previous versions of the documentation. Having been out of the loop and not very well versed in the new Launchpad system, it is a bit challenging for me to know exactly what has and hasn't been added into the mod. QUICK_EDIT
Downloaded.
But guys, how can I see in documentation what is exactly new just in 0.3?
Somebody wrote about filtering versions and I think it is a good idea too, it can save a lot of time. _________________
Changing the documentation to allow sorting or filtering features by version is not easily possible. It might be possible to generate lists like the old documentation had (the appendix), but as features are expanded, they cannot be grouped like this any more. The addition of observer flags for sides would either appear under 0.1, or all previous tags wouldn't show up under 0.1 any more.
The new features are Custom Missiles, Gattling Cycle, Whiteboy fix, and several others. For a list see the link Banshee posted. Usually, the search function works pretty well on phrases like "engineer" or "whiteboy". The only page that isn't tied to a feature though it might be important is the Migration page, which describes which tags were renamed of got a new meaning.
Graion: Everything that is finished can get in. _________________ QUICK_EDIT
If the documentation repo were current and the sections had the proper versionadded/versionchanged directives, one could at least generate a changelog from the documentation.
Changing the documentation to allow sorting or filtering features by version is not easily possible. It might be possible to generate lists like the old documentation had (the appendix), but as features are expanded, they cannot be grouped like this any more.
Well, just put somewhere at bottom new pag/sections named ,,New Features 0.3", ,,New features 0.4", so when we open it, we know exactly what is new/changed and thats it.
No need exact filtering per version.
But simply adding
,,New features 0.3"
and inside page list:
-Custom Missiles
-Gattling Cycle
-Whiteboy fix
So we can have idea what is new, so we can go though documentation manually and check it.
Without something like this, we would not know what is new in 0.3 for testing unless we go to internet. But you know, sometimes, someone may have broken connection. Then he must search though whole huge documentation to find 0.3 fixes or new features.
So Alex, if that is huge job to filter listing per version, then leave it, do not waste time, but at least simple version page would be enough. _________________
There's already a way to programatically include introduction, change and deprecation information via Sphinx directives in the documentation. (Frequently seen through the New in version 0.2. notices in the documentation.)
There's also already a way to automatically generate a changelog from that. It's primarily meant for the documentation writers themselves, but all it needs is copying and a bit markup for inclusion. (See attachment.)
Making it the way it was in the previous versions of the documentation, where parts of the docs just vanish, would be possible, but only with a disproportionate amount of work and, more importantly, it would be just plain silly. The old docs primarily did that because they weren't segmented. The new docs are. Most features or feature groups have their own pages, and if the docs are properly updated, all additions, changes and deprecations are properly marked. There's no reason to hide anything, because there can be no misunderstanding. (That and if you're using an old version of Ares with the new version of the docs, you're doing something wrong anyway.)
Generating a changelog, on the other hand, is relatively easy: There's a changelog generator/viewer for the documentation maintainers that can be used to quickly copy together a changelog for the version. It's not entirely automatic, but it shouldn't take more than half an hour, and only has to be done once per release.
Like all other documentation work, it is also code-less, plain text work that could be done by anyone...
...if one has the current documentation source files.
Since the repository hasn't been updated, I don't. Otherwise, I would already have ended this discussion by providing a changelog. I have figured out by now that most of the recent changes ended up in some weirdly-named branch, but there's no 0.3 documentation change marked.
And no, I can't figure it out from the source code, because that repository doesn't seem to be up to date, either.
Joined: 22 Nov 2010 Location: Iszkaszentgyorgy, Hungary
Posted: Fri May 10, 2013 3:30 pm Post subject:
See Bansh's post.
And I really suggest you to actually read the stuff carefully, you seem to not think at all. _________________ "If you didn't get angry and mad and frustrated, that means you don't care about the end result, and are doing something wrong." - Greg Kroah-Hartman
=======================
Past C&C projects: Attacque Supérior (2010-2019); Valiant Shades (2019-2021)
=======================
WeiDU mods: Random Graion Tweaks | Graion's Soundsets
Maintainance: Extra Expanded Enhanced Encounters! | BGEESpawn
Contributions: EE Fixpack | Enhanced Edition Trilogy | DSotSC (Trilogy) | UB_IWD | SotSC & a lot more... QUICK_EDIT
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum