Menu
▾
▴
Re: [Tiki-devel] Tiki 8 BRANCHED
|
From: Torsten F. <to...@fa...> - 2011-10-04 18:48:38
|
> I hope everyone can switch at least one site they're working on during > the testing process, it really helps to have as many eyeballs on the > stable branch at this time as is possible. Yes and I do with a nearly semi productive one, a site that might be going big - we'll see. It was on trunk for a while and will upgrad to the latest 8 Branches tonight. maybe going 9 when Devs ask for - I might split public area and Intranet for that and test 9 on intranet. But please, please Devs: do NOT deprecate the wikistructure-menu module!!! Who else has a site for Tiki 8? Cheers Torsten Am 04.10.2011 15:54, schrieb Jonny Bradley: > > Hi all > > Once again thanks to Philippe and Nelson for getting this done - as > expected i don't really have time to do the full co-ordinator role > properly this time. > > A few of comments inline below... > > On 3 Oct 2011, at 07:00, Filipus Klutiero wrote: > >> Hi, >> Nelson just made a small commit to SVN, but one that represents a >> giant leap for Tiki 8 ( http://dev.tiki.org/Tiki8 ). >> As recently announced, tonight we created the 8.x branch, which will >> lead to Tiki 8.0 at the end of October. We're truely entering release >> mode now. >> >> That means the trunk "branch" is now split in two: a new trunk, and 8.x. >> >> >> What changes >> >> >> The new trunk is now again open to any development, no need to >> contact release coordinators to work there anymore. Commits to trunk >> will now ship for the first time in Tiki 9, our next "LTS" version >> (scheduled for April 2012). >> 8.x, on the other hand, is now truely frozen. Committing anything >> other than fixes (and new translations) to 8.x should be exceptional. >> There is no proposals branch at this time (and until further notice), >> so you can commit any fix to 8.x directly. See >> https://dev.tiki.org/Where+to+commit for more details on what is >> acceptable in a stability branch. >> >> Developers will now have to commit on trunk or 8.x depending on the >> content. Here is what I did to be able to work on both 8.x and trunk >> (that is, to get a checkout of both): >> I updated my trunk checkout to the latest revision (r37900). >> I copied my "trunk" folder to a "8.x" folder. >> I switched my 8.x folder to branch 8.x. This can be done with >> >>> svn switch >>> https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/8.x >> This might need an update after. http://dev.tiki.org/Update > > Personally i do a fresh checkout of new branches - e.g. by using > > svn co > https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/branches/8.x > > > /I like that fresh clean feeling! :)/ > > (details > here: http://dev.tiki.org/get%20code#Using_Stable_8.x_branch_from_SVN) > >> We are now in a semi-automatic merging period: >> http://dev.tiki.org/Semi-automatic+merging+period >> This means fixes that apply to both trunk and 8.x do not need to be >> done on both manually. Commits to 8.x will be merged >> semi-automatically to trunk, every week or so. > > I'd say that is far too infrequent and it should be done every day or > two if possible. One of the most painful things about this time are > conflicts, and the longer merging is left the worse things can get. > > When there aren't any conflicts it's quite easy - simple instructions > are here: > > http://dev.tiki.org/SVNTips#Merging_branch_to_trunk_while_releasing > > > (and anyone with commit access can do it - hint hint!) > > Sometimes getting the first one done is a bit of a pain - i'm trying > to do that now... >> >> >> Freeze exceptions >> >> Changes other than fixes should be exceptional on 8.x. If you change >> something just for enhancing and break something, you take the entire >> responsability for the breakage. Changes other than fixes may be >> reverted even if we don't know of any specific breakage they cause. >> If you're unsure about whether a change qualifies for 8.x or not, or >> want to request an exception, please contact the release coordination >> team, consisting of Jonny Bradley (jonnyb), Nelson Ko (nkoth) and >> myself (chealer). At least one of us is on IRC most of the time. > > For instance... i'd like to back-port r37950 /[REF] remove obsolete > headerlib code for hasDoneOutput control (unused since removal of > xajax)/ to 8.x to avoid possible conflicts later - i'd been testing it > on my home localhost for several weeks but couldn't commit before the > branch as i was away - let's discuss on irc >> >> >> Road ahead >> >> >> >> Now that we're branched, the only thing we need to do to release Tiki >> 8 is to stabilize the 8.x branch. According to the plan, that should >> take about one month: http://dev.tiki.org/Tiki8 >> The next item on the schedule is Tiki 8 beta, and is already coming >> on October 6th, that is in 3 days. The plan is to have a single beta >> and a single release candidate as only pre-releases, and to release >> 8.0 on October 27th, which is less than 4 weeks from now. This >> schedule is aggressive. Therefore, the freeze will be enforced quite >> strictly; dealing with existing bugs will be challenging enough. For >> developers, the week of October 9th will be particularly intense, >> when we'll start dogfooding Tiki 8 on Tiki community sites. >> Jean-François will upgrade themes.tiki.org <http://themes.tiki.org> >> and tv.tiki.org <http://tv.tiki.org>, then dev.tiki.org >> <http://dev.tiki.org> and finally doc.tiki.org <http://doc.tiki.org>. >> Most of our websites will be upgraded over the course of 5 days. >> Everyone's contribution will be needed to make this happen on >> schedule. Even though dogfooding should catch most issues, we need >> testers to try 8.x in various environments. Of course, we also need >> people to fix the bugs found... > > Can't wait! :) > >> >> Current issues >> >> >> >> So here is what's on the radar for now. If you feel a right of >> ownership on the following regressions, feel free to fix: >> >>> * Comment moderation is partially broken. Messages warning >>> the >>> >>> user before and after posting a comment needing moderation do >>> not appear >>> >>> anymore. Chealer 20110824 (r36462) >>> >>> >>> * Autocompletion is attempted by the Username field in Switch >>> >>> >>> User (Login module) when AJAX is off but jQuery autocomplete >>> enabled, >>> >>> resulting in the error message "Required features: >>> feature_ajax, >>> >>> feature_jquery_autocomplete. If you do not have the privileges >>> to >>> >>> activate these features, ask the site administrator." being >>> printed. >>> >>> It's not clear why this doesn't happen on 7.x (it gets the >>> same AJAX >>> >>> reply). The hourglass keeps spinning on trunk. Chealer >>> 20110826 (r36508) >>> > > Will take that one... > >>> * >>> >>> >>> >>> * Quizzes do not display anymore ("Undefined index: >>> >>> tiki_p_take_quiz"). list_quizzes() is broken since >>> get_permissions() >>> >>> does not return what get_permission_names_for() expects >>> starting from >>> >>> r34025. Chealer 20110921 r37481 >>> >>> >>> * Newsletters do not display and cannot be created anymore >>> >>> ("Undefined index: tiki_p_admin_newsletters"). Presumably the >>> same issue >>> >>> as above. Chealer 20110928 >>> >>> wiki page alias are no longer working. See bottom of >>> https://trunkdoc.tiki.org/Hotwords >> >> >> If you don't, don't be too shy to help anyway ;-) >> We are relying on everyone to identify regressions, so please list >> those you find, but remember to put enough information to facilitate >> reproducing and to allow contacting you. Simply reporting that "x >> doesn't work" may not work to get the problem fixed ;-) >> >> There are still unclaimed open Todo items on >> http://dev.tiki.org/Tiki8#Todo Note that we will not verify the >> status of those before the release, unless they are claimed. >> >> Thanks for your attention, and now, <INSERT MOTIVATIONAL STATEMENT HERE>! >> Philippe, on behalf of the Tiki 8 release coordination team > > > Thanks again Philippe - Tiki 8 will be a fantastic Tiki i think!! > > I hope everyone can switch at least one site they're working on during > the testing process, it really helps to have as many eyeballs on the > stable branch at this time as is possible. > > On that note, best get on with it! > > jonny > >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense. >> http://p.sf.net/sfu/splunk-d2dcopy1_______________________________________________ >> TikiWiki-devel mailing list >> Tik...@li... >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > > > _______________________________________________ > TikiWiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |