On Tue, 2005-04-05 at 15:42 -0600, Elijah Newren wrote:
> Hi,
>
> On Apr 5, 2005 3:28 PM, JP Rosevear <[EMAIL PROTECTED]> wrote:
>
> > I would suggest that during the period during the release candidate and
> > code freeze we announce code changes to [EMAIL PROTECTED] (just like we do
> > at othe
On Sat, 2005-04-09 at 12:34 +0100, Bill Haneman wrote:
> Murray Cumming wrote:
> >We already say "API freeze is not required for non-platform libraries,
> >but is recommended."
> >
> This is not as strong a position as seemed to be agreed when this thread
> came up before:
>
> http://mail.gnome.o
Murray Cumming wrote:
On Wed, 2005-04-06 at 13:37 +0100, Bill Haneman wrote:
I thought we agreed near the end of the 2.12 cycle that an API freeze
for non-core exported APIs should be added to the release schedule.
We already say "API freeze is not required for non-platform libraries,
but
On Wed, 2005-04-06 at 13:37 +0100, Bill Haneman wrote:
> I thought we agreed near the end of the 2.12 cycle that an API freeze
> for non-core exported APIs should be added to the release schedule.
We already say "API freeze is not required for non-platform libraries,
but is recommended."
Persona
I thought we agreed near the end of the 2.12 cycle that an API freeze
for non-core exported APIs should be added to the release schedule.
There was discussion of several options, including:
(1) requiring all exported APIs to follow the platform API freeze
dates, or;
(2) having a 'non core API
Hi,
On Apr 5, 2005 3:28 PM, JP Rosevear <[EMAIL PROTECTED]> wrote:
> I would suggest that during the period during the release candidate and
> code freeze we announce code changes to [EMAIL PROTECTED] (just like we do
> at other times for string/ui changes). Just prompts maintainers to step
> ba
On Wed, 2005-04-06 at 04:18 +1000, Jeff Waugh wrote:
> Hi all,
>
> Here's the proposed schedule for GNOME 2.12. Very little has changed, we've
> just pulled back the release candidate a week, but left the code freeze one
> week before final. Hopefully this will net more testers, without too much
>
> Please follow up with comments. If there are no major bugs, this proposal
> will be cast in stone as our final 2.12 schedule on Monday. :-)
Apologies, that should be Friday.
- Jeff
--
GUADEC 2005: May 29th-31st http://2005.guadec.org/
"Spend your 'differ
Hi all,
Here's the proposed schedule for GNOME 2.12. Very little has changed, we've
just pulled back the release candidate a week, but left the code freeze one
week before final. Hopefully this will net more testers, without too much
bureaucracy fixing their bugs in the very final stages of the re
