Looks like we'll need an new maven-ical-report for the site generation.

To inject the schedule into the site, with links to the live-schedule.

- 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 we'll
> get wiki fleshed out with details of the issues listed in JIRA.
>
> Jason.
>
>> -----Original Message-----
>> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
>> 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
>> Maven itself, Doxia, Wagon and some plugins I'm working on I have a
>> clear idea of when they will be released. But what the Mylar team
>> 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
>> ultimately schedule but I would like to make a start at trying to
>> provide some transparency as the Mylar team does.
>>
>> So the though was that we would have a calendar on Google where
>> 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
>> releases. I planned 4 weeks between the last releases and it ended 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 look
>> for planned releases dates.
>>
>> I would like to set this up asap.
>>
>> +1
>>
>> Jason.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to