Return-Path: Delivered-To: apmail-maven-doxia-dev-archive@www.apache.org Received: (qmail 10125 invoked from network); 22 Jan 2008 13:03:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Jan 2008 13:03:32 -0000 Received: (qmail 77862 invoked by uid 500); 22 Jan 2008 13:03:22 -0000 Delivered-To: apmail-maven-doxia-dev-archive@maven.apache.org Received: (qmail 77829 invoked by uid 500); 22 Jan 2008 13:03:22 -0000 Mailing-List: contact doxia-dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: doxia-dev@maven.apache.org Delivered-To: mailing list doxia-dev@maven.apache.org Received: (qmail 77820 invoked by uid 99); 22 Jan 2008 13:03:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jan 2008 05:03:22 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [212.27.42.28] (HELO smtp2-g19.free.fr) (212.27.42.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jan 2008 13:03:07 +0000 Received: from smtp2-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp2-g19.free.fr (Postfix) with ESMTP id 776AC12B739 for ; Tue, 22 Jan 2008 14:02:58 +0100 (CET) Received: from [192.168.0.11] (lam60-1-82-233-128-14.fbx.proxad.net [82.233.128.14]) by smtp2-g19.free.fr (Postfix) with ESMTP id 320B212B732 for ; Tue, 22 Jan 2008 14:02:58 +0100 (CET) Message-Id: From: Vincent Massol To: doxia-dev@maven.apache.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Subject: Breaking changes on Doxia trunk ok? Date: Tue, 22 Jan 2008 14:02:57 +0100 X-Mailer: Apple Mail (2.915) X-Virus-Checked: Checked by ClamAV on apache.org Hi, I'm just starting development on Doxia and I need to understand the strategy since I need to make lots of breaking changes to accomodate the XWiki use cases (I'm planning to replace XWiki's rendering engine from Radeox to Doxia). I've just talked to VincentS and Lukas and the consensus I got was that I could just commit away on trunk and make breaking changes since: a) 1.0 has not been released yet and the API is not final and thus it's the right time to do this b) there an alpha branch that the current Doxia users (like Maven itself) can use id they don't want to upgrade to the changes made. So I'd like agreement that I can make my changes on trunk. Namely I'd like to implement these (and more to come): * http://jira.codehaus.org/browse/DOXIA-203: Add support for level 6 sections and generalize Sink API for sections * http://jira.codehaus.org/browse/DOXIA-202: Add an API for getting a tree of syntax blocks * http://jira.codehaus.org/browse/DOXIA-165: Add support for macros * http://jira.codehaus.org/browse/DOXIA-164: Add support for strikethroughs * http://jira.codehaus.org/browse/DOXIA-163: Add support for underscores * http://jira.codehaus.org/browse/DOXIA-204: Add generic parameters support to Figure and Link events * http://jira.codehaus.org/browse/DOXIA-205: Add new standard parameters to figure sink API * http://jira.codehaus.org/browse/DOXIA-206: Add new standard parameters to link sink API * http://jira.codehaus.org/browse/DOXIA-207: Add events for recognizing words in the Sink API WDYT? Thanks -Vincent