On Sunday 27 July 2008, Aaron J. Seigo wrote:
> in addition to that, i think we really ought to get together at Akademy and
> discuss what we want for the release schedule for 4.3.
+1 from me. Allen Winter's proposal of the same schedule, just time-shifted
seems to mostly (by coincidencde?) addr
Op zondag 27 juli 2008 13:48 schreef u:
> Howdy,
>
> I published an initial version of the schedule we discussed the past few days.
> http://techbase.kde.org/Schedules/KDE4/4.2_Release_Schedule
>
> Please review.
>
> -Allen
Looks perfect to me.
Toma_
Howdy,
I published an initial version of the schedule we discussed the past few days.
http://techbase.kde.org/Schedules/KDE4/4.2_Release_Schedule
Please review.
-Allen
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/list
Op zondag 27 juli 2008 00:32 schreef u:
> I took into account Dirk's concerns and my own feelings/observations
> and made a counter proposal.
Allen, sorry for my earlier reply. That wasn't fair.
Your proposal is fine. You added a Alpha release compared to my proposal. I
don't see a need for th
On Saturday 26 July 2008, Allen Winter wrote:
> We really should decide on a schedule soon. Or do you guys want to wait
> for Akademy?
personally, for 4.2 i think we should stick with the same 6 month cycle as we
had for 4.1. we ought to have a schedule by the time 4.1.0 is released and
we'll p
On Wednesday 16 July 2008 11:41:11 Tom Albers wrote:
> Op woensdag 16 juli 2008 15:12 schreef u:
> > I think we should keep the same schedule from 4.1,
>
> You totally ignore my proposal. Please respond to that thread.
>
Sorry, I didn't mean to give that impression.
I took into account Dirk's co
ng I'd also like to discuss during Akademy, I understand you
won't be there, so we should make sure we are aware of your thoughts, concerns
and input in general.
> > When do we hard-freeze? (Around beta2 looks sensible to me...)
>
> The hard feature freeze would occur on
Op woensdag 16 juli 2008 15:12 schreef u:
> I think we should keep the same schedule from 4.1,
You totally ignore my proposal. Please respond to that thread.
Toma___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/re
" of 4.1. It felt right to me.
Of course, I wasn't really developing any new features at all -- simply trying
to get kdepim into a working state.
Please explain how "always summer in trunk" would work.
> When do we hard-freeze? (Around beta2 looks sensible to me...)
>
On Wednesday 16 July 2008 15:12:07 Allen Winter wrote:
> On Monday 16 June 2008 12:12:08 Tom Albers wrote:
> I noticed that today's RC1 announcement mentions that 4.2 is expected in
> January. So we should probably publish the 4.2 schedule on TechBase
> soonish.
Agree.
> I
ease RC 1
> ~30 January Release Final
>
I noticed that today's RC1 announcement mentions that 4.2 is expected in
January.
So we should probably publish the 4.2 schedule on TechBase soonish.
I think we should keep the same schedule from 4.1,
except time-shifted forward 6months, like s
On Wednesday 09 July 2008, Tom Albers wrote:
> So we are stuck to a large freeze period for ever?
What is the thing that you're most concerned about? that a long freeze period
causes development to stall, or that it causes development to branch off in
work-branches, private repositories, git tr
Op maandag 07 juli 2008 14:46 schreef u:
> On Monday 16 June 2008, Sebastian Kuegler wrote:
>
> > > So, all in all, that would be something like:
> > > August - early December: free hacking
>
> 4 months without a release ? or do you expect 4 months of weekly snapshot
> releases to appear?
>
> >
On Monday 16 June 2008, Sebastian Kuegler wrote:
> > So, all in all, that would be something like:
> > August - early December: free hacking
4 months without a release ? or do you expect 4 months of weekly snapshot
releases to appear?
> > ~15 December Release Beta 1
> > ~3 January Release Bet
On Monday 16 June 2008 18:12:08 Tom Albers wrote:
> As we are approaching the final 4.1 release, I think we can think about the
> schedule for 4.2 a bit and brainstorm about what we like and don't like. To
> kick off the discussion, let me throw some ideas around.
>
> Because we became a lot more s
Hi,
As we are approaching the final 4.1 release, I think we can think about the
schedule for 4.2 a bit and brainstorm about what we like and don't like. To
kick off the discussion, let me throw some ideas around.
Because we became a lot more stable during the 4.1 development, I think we can
16 matches
Mail list logo
