Yes Steven, I agree with all you have said below. I'm +1 for merging OL back to the trunk.
Steven M. Ottens wrote: > It would be best if would have this list of files and use the merger > to get rid of all 'old' files. But the list isn't ready yet, so I > prefer to move everything, including potential old files back to > trunk. Then we can create /mapbuilder/archive were we can start > moving old files/not ol-compatible files to. > So this merge only serves to get development back to trunk where it > should be by now. Almost everything, if not everything is working in > ol-integration so it can replace trunk. The problem is not that ol- > integration falls short of trunk, but it has redundant files. > We can prune those in ol-integration or in trunk. I prefer trunk. > This way it's clear for us and others that we're committed to the ol- > integration and we have to get it finished and focus our efforts on > getting the updated trunk released. > > just my 3.14 cents > Steven > > On Jun 28, 2007, at 9:04 PM, Diez, Matthew wrote: > > >> On the one hand, we want/need to get this process started. >> >> Do we have a complete list someplace of what widgets we're keeping, >> which ones we're tossing, etc? >> >> I'd like to get a feel for that before I -1 or +1 it. >> >> In general, leaning towards getting started on this, but, I think it >> should only proceed with a full knowledge of what needs >> to be pruned or modified from trunk. >> >> Matthew D. Diez >> >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of >> Steven M. Ottens >> Sent: Thursday, June 28, 2007 6:37 AM >> To: '[email protected]' >> Subject: [Mapbuilder-devel] merging back to trunk + release issues >> >> Hi all, >> >> The general feeling at the last meeting was that we should merge >> back to >> trunk this coming week. Are there any objections against this, I'd >> like >> to have at least a vote from each of the PSC members. If there are no >> objections this means that someone needs to merge it back. If no one >> else volunteers, I can do it on Friday 6th of July. >> Also once the merge has succeeded we can set a release date for an RC. >> I'm in favor of a RC release when all the demos are working. For a >> full >> release I'd like to have all the *.js jira issues handled for those js >> files we put in the release. >> >> Regards, >> Steven >> >> >> >> ---------------------------------------------------------------------- >> -- >> - >> This SF.net email is sponsored by DB2 Express Download DB2 Express C - >> the FREE version of DB2 express and take control of your XML. No >> limits. >> Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> mapbuilder-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel >> >> IEM CONFIDENTIAL INFORMATION PLEASE READ OUR NOTICE: >> http://www.iem.com/e_mail_confidentiality_notice.html >> >> > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > mapbuilder-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel > > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ mapbuilder-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
