From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 7B3197EE25 for ; Wed, 6 Nov 2013 16:25:51 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of amc79@cam.ac.uk) identity=pra; client-ip=131.111.8.142; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="amc79@cam.ac.uk"; x-sender="amc79@cam.ac.uk"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of amc79@cam.ac.uk) identity=mailfrom; client-ip=131.111.8.142; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="amc79@cam.ac.uk"; x-sender="amc79@cam.ac.uk"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@ppsw-42.csi.cam.ac.uk) identity=helo; client-ip=131.111.8.142; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="amc79@cam.ac.uk"; x-sender="postmaster@ppsw-42.csi.cam.ac.uk"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtsCAKheelKDbwiOnGdsb2JhbABQCoM/rSuSXoEkFg4BAQEBAQYNCQkUKIIlAQEEAW4LBQsLGA0hISQSBhMSAodbAwkGBAm1EQMKV4kUjGeBL4EQMweDIIEQA5YhgxqFDoYVhyCBPg X-IPAS-Result: AtsCAKheelKDbwiOnGdsb2JhbABQCoM/rSuSXoEkFg4BAQEBAQYNCQkUKIIlAQEEAW4LBQsLGA0hISQSBhMSAodbAwkGBAm1EQMKV4kUjGeBL4EQMweDIIEQA5YhgxqFDoYVhyCBPg X-IronPort-AV: E=Sophos;i="4.93,647,1378850400"; d="scan'208";a="34043025" Received: from ppsw-42.csi.cam.ac.uk ([131.111.8.142]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 06 Nov 2013 16:25:50 +0100 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from [37.157.39.238] (port=1332 helo=[10.2.5.234]) by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1Ve4zN-0004TQ-92 (Exim 4.82_3-c0e5623) (return-path ); Wed, 06 Nov 2013 15:25:49 +0000 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Wed, 6 Nov 2013 15:25:51 +0000 Cc: caml users , infrastructure Content-Transfer-Encoding: quoted-printable Message-Id: <91D4ED80-5443-4ED2-9B0C-95DBCE49A7D7@cam.ac.uk> References: <6386BA74-F9BF-4283-A298-ABE30B3A458E@cam.ac.uk> To: Kakadu X-Mailer: Apple Mail (2.1510) Subject: Re: [Caml-list] Migration plan and bug hunt for ocaml.org - http://preview.ocaml.org Dear Kakadu,=20 Yes, they'll be tagged as `redesign` but there may be a delay between submi= tting an issue and seeing it tagged. Apologies for that but don't worry ab= out submitting duplicates as we'll cross reference and close any dupes as w= e triage. Thanks! Amir On 6 Nov 2013, at 13:31, Kakadu wrote: > Amir, >=20 > Are all bugs related to redesign are marked with `redesign` tag? I > ask, because very small count of opened bugs are tagged with > `redesign`. Can I rely on tagged questions when I will check is my > bug reported or not? >=20 > Kind regards, > Kakadu >=20 > On Wed, Nov 6, 2013 at 2:31 PM, Amir Chaudhry wrote: >> Dear caml-list, >>=20 >> We're close to releasing the new design of ocaml.org but need help from = the community to identify and fix bugs before we switch next week. >>=20 >> Ashish, Christophe, Philippe and I have been discussing how we should go= about this and below is the plan for migration. If you'd like to discuss = any of this, then the infrastructure list is the best place to do so (cced). >>=20 >> 1. We've made a new branch on the main ocaml.org repository [1] with the= redesign. This branch is a fork of the main one and we've simply cleaned = up and replayed our git commits there. >>=20 >> 2. We've built a live version of the new site, which is visible at http:= //preview.ocaml.org - this is rebuilt every few minutes from the branch men= tioned above. >>=20 >> 3. Over the course of one week, we ask the community to review the new s= ite and report any bugs or problems on the issue tracker [2]. We triage tho= se bugs to identify any blockers and work on those first. This is the phas= e we'll be in from *today*. >>=20 >> 4. After one week (7 days), and after blocking bugs have been fixed, we = merge the site into the main branch. This would effectively present the ne= w site to the world. >>=20 >> During the above, we would not be able to accept any new pull requests o= n the old site but would be happy to accept them on the new branch. Hence,= restricting the time frame to one week. >>=20 >> Please note that the above is only intended to merge the *design* and *t= oolchain* for the new site. Specifically, we've created new landing pages,= have new style sheets and have restructured the site's contents as well as= made some new libraries [3, 4]. The new toolchain means people can write = files in markdown, which makes contributing content a lot easier. >>=20 >> Since the files are on GitHub, people don't even need to clone the site = locally to make simple edits (or even add new pages). Just click the 'Edit = this page' link in the footer to be taken to the right file in the reposito= ry and GitHub's editing and pull request features will allow you to make ch= anges and submit updates, all from within your browser [5]. >>=20 >> There is still work to be done on adding new features but the above chan= ges are already a great improvement to the site and are ready to be reviewe= d and merged. >>=20 >> [1] https://github.com/ocaml/ocaml.org/tree/redesign >> [2] https://github.com/ocaml/ocaml.org/issues >> [3] http://pw374.github.io/posts/2013-09-05-22-31-26-about-omd.html >> [4] http://pw374.github.io/posts/2013-10-03-20-39-07-OPAMaging-MPP.html >> [5] https://help.github.com/articles/creating-and-editing-files-in-your-= repository >>=20 >> Best wishes, >> Amir >>=20 >> -- >> Caml-list mailing list. Subscription management and archives: >> https://sympa.inria.fr/sympa/arc/caml-list >> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners >> Bug reports: http://caml.inria.fr/bin/caml-bugs