BTW, this is also something we should be doing for every release to note even what has changed, features, etc. Some things aren't so easily describe-able in the commit messages, and might need a guide.
Here is how Inkscape handles the release notes, which is what this page is describing: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.48.1 I went ahead and tweaked the transition guide to be our standard release notes with transition guide which we should be doing for every release. It is very thorough. Thanks Christopher for spearheading that effort! rg1024, great if you can add some notes up there about your changes when you get a chance. Great! http://www.aikiframework.org/wiki/Release_Notes/0.9 Jon On Fri, Jun 3, 2011 at 10:18 AM, Christopher Adams <[email protected]> wrote: > Roger, > > Please document this clearly in the transition guide: > http://www.aikiframework.org/wiki/Version_0.9_Transition_Guide > > This is particularly important if the output changes, but also if > there are new features in the markup. > > Each section in the Transition guide should look like: > > ===Title=== > > Brief description > > Code example if necessary > > ====What has changed==== > > What is different from the last version of Aiki or the way things are > normally done? > > ====What you can do==== > > Show how any new features can be utilized. > > ====What you MUST do==== > > These are changes that site designers MUST make to existing sites to > accommodate this change. > > > > *Please write the transition guide in clear and complete sentences. > > > > - Christopher > > > > On Fri, Jun 3, 2011 at 11:07 AM, Roger Martín <[email protected]> wrote: >> I started working on forms.php. >> Changes: >> - now you can call the form with your name >> # (form: add: 17) # = # (form: add: aiki_users) # >> - Have changed the id, class and names of the form. >> div container: FORM_NAME_container >> id form: form_FORM_NAME >> name = FORM_NAME >> class = "FORM_NAME edit_form | new_record_form" >> EX: aiki_users_container, form_aiki_users, aiki_users, "aiki_users >> new_record". >> Perhaps CSS breaks now >> >> The next step is add html attributes like: >> >> #(form:add:aiki-users:no-ajax: :id=user|class=myclass|onsubmit=validate()" >> that must a generate a form with >> <form ..id="user" class="myclass" onsubmit="validate()"... >> >> This sintaxis is not very clear..but is compatible with previous version and >> very flexible: we can add all html attributes.. >> >> PD: yes..i will documented it and search bugs and blueprint affected by >> this.. >> >> have a nice weekend!! >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~aikiframework-devel >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~aikiframework-devel >> More help : https://help.launchpad.net/ListHelp >> >> > > > > -- > ——— > christopher adams > 86 186 1172 0021 | 1 646 201 3335 > 49 15 156 219931 | 886 953 036 630 > chris.raysend.com > > _______________________________________________ > Mailing list: https://launchpad.net/~aikiframework-devel > Post to : [email protected] > Unsubscribe : https://launchpad.net/~aikiframework-devel > More help : https://help.launchpad.net/ListHelp > -- Jon Phillips http://rejon.org/ | http://fabricatorz.com/ chat/skype: kidproto | irc: rejon +1.415.830.3884 (global) | +1-510-499-0894 (sf) +86-187-1003-9974 (beijing) _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
