That sounds like a great idea...and one less place to visit.
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Monday, April 02, 2007 3:23 PM
To: Maven Developers List
Subject: RE: Creating a schedule for releases
I know the calendar is already out there so this
e,
but it could also incorporate the releases of all plugins, including
ones where the lead isn't on the PMC (if there are any).
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Monday, April 02, 2007 12:08 PM
To: Maven Developers List
Subject: Re: Creating a s
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 som
+1 Spiffy idea!
- Joakim
Jason van Zyl wrote:
> 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 s
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
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 e
After trying to schedule some stuff I noticed without different
calendars the colour of everything is the same so I created separate
calendars for the sub-projects and another for plugins so that folks
can visually distinguish the releases.
Jason.
On 2 Apr 07, at 10:32 AM 2 Apr 07, Emmanue
+1
Emmanuel
Jason van Zyl a écrit :
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
On 02/04/2007, at 11:55 PM, Jason van Zyl wrote:
There is no reason why we shouldn't be able to do this.
Totally agree. And drawing this information into a known, persistent,
and up-to-date location can only help get more people involved. The
most successful releases will come when 3, 4 o
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 cu
On 2 Apr 07, at 9:44 AM 2 Apr 07, Brett Porter wrote:
+1, I had a draft mail saying roughly the same thing.
We will probably still need to be occasionally flexible depending
on availability of people, too, but as we start whipping out non-
alpha releases of some of the underlying stuff and
+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.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Monday, April 02, 2007 9:38 AM
To: Maven Developers List
Subject: Creating a schedu
+1, I had a draft mail saying roughly the same thing.
We will probably still need to be occasionally flexible depending on
availability of people, too, but as we start whipping out non-alpha
releases of some of the underlying stuff and increasing the general
amount of testing, it'll be much
12 matches
Mail list logo
