hm okay well its not a blocker I think. I didn't notice that one at all. Lets wait a couple of days, I think its okay. We cannot delete the build anyway, after 100 downloads the delete button in googlecode-download page is no more available, so we would need to create a 1.8.1 release. I would like to wait with such a release because its a documentation issue, no app-error or blocker.
Regarding the TAG and TRUNK tree in our SVN and release package process: TRUNK is now 1.9 If we encounter some issue (actually issues similar to this :)) where we would like to provide a bugfix/hotfix for older/already released branch, we would commit this into the TAG/1_8/ tree, build TAG/1_8 it and release it as 1.8.1 ... or if additional hotfix its necessary we release as 1.8.2, 1.8.3 ... et cetera. You agree with that? I don't think its necessary to have additionally 1.8.1 as separated TAGs, but having the major steps like 1.8, 1.9, 2.0 et cetera as separated TAG/branch is quite handy so we can still provide hotfixes for old branches without big puzzling. Sebastian 2011/9/14 Maxim Solodovnik <[email protected]> > Hello Sebastian, > > I just checked in install_welcome_EN.**vm > it was updated with valid properties need to be edited > maybe it make sense to recreate release build to have this change? > > -- > WBR > Maxim aka solomax > -- Sebastian Wagner http://www.webbase-design.de http://openmeetings.googlecode.com http://www.wagner-sebastian.com [email protected] -- You received this message because you are subscribed to the Google Groups "OpenMeetings developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/openmeetings-dev?hl=en.
