Return-Path: Delivered-To: apmail-maven-dev-archive@www.apache.org Received: (qmail 3868 invoked from network); 2 Apr 2007 20:23:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Apr 2007 20:23:49 -0000 Received: (qmail 52667 invoked by uid 500); 2 Apr 2007 20:23:54 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 52606 invoked by uid 500); 2 Apr 2007 20:23:54 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 52595 invoked by uid 99); 2 Apr 2007 20:23:54 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2007 13:23:54 -0700 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (herse.apache.org: transitioning domain of brianf@reply.infinity.nu does not designate 205.210.42.54 as permitted sender) Received: from [205.210.42.54] (HELO mx-outbound01.easydns.com) (205.210.42.54) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2007 13:23:45 -0700 Received: from intrepid.infinity.nu (c-24-128-239-207.hsd1.nh.comcast.net [24.128.239.207]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx-outbound01.easydns.com (Postfix) with ESMTP id AECD17F7B for ; Mon, 2 Apr 2007 16:21:03 -0400 (EDT) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: Creating a schedule for releases X-MIMEOLE: Produced By Microsoft Exchange V6.5 Date: Mon, 2 Apr 2007 16:23:22 -0400 Message-ID: <2BABBE7D2A66E04DB8A66A527D29927E25E1CA@intrepid.infinity.nu> In-Reply-To: <8D9C7048-9C85-4E5F-ACCA-08A9B730DA41@maven.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Creating a schedule for releases Thread-Index: Acd1QS69XhbJqv+ERFKzyb+cCQAS6QAI04yg References: <14DAADBF-C0BC-4278-916B-2E381592A37A@maven.org> <2BABBE7D2A66E04DB8A66A527D29927E25E1C2@intrepid.infinity.nu> <46112887.7040506@erdfelt.com> <8D9C7048-9C85-4E5F-ACCA-08A9B730DA41@maven.org> From: "Brian E. Fox" To: "Maven Developers List" X-Virus-Checked: Checked by ClamAV on apache.org I know the calendar is already out there so this might be late info (I didn't think of it before), but I thought I'd point out that Jira has the ability to set release dates and there is a calendar portlet you can add to show them. It's probably less functionality than the google one, but it could also incorporate the releases of all plugins, including ones where the lead isn't on the PMC (if there are any).=20 -----Original Message----- From: Jason van Zyl [mailto:jason@maven.org]=20 Sent: Monday, April 02, 2007 12:08 PM To: Maven Developers List Subject: Re: Creating a schedule for releases On 2 Apr 07, at 12:00 PM 2 Apr 07, Joakim Erdfelt wrote: > Looks like we'll need an new maven-ical-report for the site=20 > generation. > > To inject the schedule into the site, with links to the live-schedule. > I think just pointing to the calendar will suffice. I think a lot of people will just end up subscribing to the feed. Jason. > - Joakim > > Jason van Zyl wrote: >> >> On 2 Apr 07, at 9:44 AM 2 Apr 07, Brian E. Fox wrote: >> >>> +1. More info helps the users to plan and gives the devs >>> something to >>> work towards. I'd like to see some tentative plans for 2.1 also. >>> >> >> 2.1-alpha-1 will go on the schedule, the issues are registered for it >> and John and I would like to cut the alpha in the coming week so=20 >> we'll get wiki fleshed out with details of the issues listed in JIRA. >> >> Jason. >> >>> -----Original Message----- >>> From: Jason van Zyl [mailto:jason@maven.org] >>> Sent: Monday, April 02, 2007 9:38 AM >>> To: Maven Developers List >>> Subject: Creating a schedule for releases >>> >>> Hi, >>> >>> Taking the lead from the Mylar development team, whom I have a great >>> deal of respect for, I would like to create a shared Google calendar >>> where we can put some releases on schedules. I know at least for=20 >>> Maven itself, Doxia, Wagon and some plugins I'm working on I have a=20 >>> clear idea of when they will be released. But what the Mylar team=20 >>> does is work under the general Europa guidelines and they try and do >>> releases every 6 weeks. So I'm not sure how the everything will be=20 >>> ultimately schedule but I would like to make a start at trying to=20 >>> provide some transparency as the Mylar team does. >>> >>> So the though was that we would have a calendar on Google where=20 >>> everyone on the PMC has access to the schedule (as it's a PMC person >>> who has to do a release) and I'll start the by putting in the Maven=20 >>> releases. I planned 4 weeks between the last releases and it ended=20 >>> up being 6 so I'll shoot for that again, but even if we're off a bit >>> it keeps the users informed and they will have a single place to=20 >>> look for planned releases dates. >>> >>> I would like to set this up asap. >>> >>> +1 >>> >>> Jason. >>> >>> -------------------------------------------------------------------- >>> - >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For=20 >>> additional commands, e-mail: dev-help@maven.apache.org >>> >>> >>> -------------------------------------------------------------------- >>> - >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For=20 >>> additional commands, e-mail: dev-help@maven.apache.org >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For=20 >> additional commands, e-mail: dev-help@maven.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For=20 > additional commands, e-mail: dev-help@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org