On Wed, Jun 5, 2013 at 12:52 PM, Martijn Brekhof <m.brek...@gmail.com> wrote:
> When is this going live? According to the ObjectiveMaintenanceSchedule
> http://wiki.lpi.org/wiki/ObjectiveMaintenanceSchedule

Anke is correct, expect these changes in October.

The Maintenance Schedule is more of a 'if no force acts upon us to
change the schedule'.  And needs updating to reflect the retirement of
the 301/302 exams.  In this case, the force acting upon us with a way
of removing the 301 obstacle to LPIC-3 certification for people much
more interested in the 303/304 exams.

Regards,
--matt
>
>
>
> On Wed, Jun 5, 2013 at 5:16 PM, G. Matthew Rice <m...@starnix.com> wrote:
>>
>> Hi everyone,
>>
>> There has been a lot of clean up of the objectives over the last month
>> since they were first announced on the list.
>>
>> It would be nice to get everyone's feedback on this version:
>>
>>     http://wiki.lpi.org/wiki/LPIC-2_Objectives_V4
>>
>> There's a short summary of the changes that have been made here:
>>
>>     http://wiki.lpi.org/wiki/LPIC2SummaryVersion3To4
>>
>> I'm sure that there will be something in there for each of you to love
>> (and, probably, hate, that's how it goes :)).
>>
>> I doubt that there will be any significant changes at this point.
>> Maybe some clarifications/addendums like we've done in the past:
>>
>>     http://wiki.lpi.org/wiki/LPIC-2_Objectives#Addenda
>>
>> Regards,
>> --
>> G. Matthew Rice <mr...@lpi.org>                         gpg id: EF9AAD20
>> _______________________________________________
>> lpi-examdev mailing list
>> lpi-examdev@lpi.org
>> http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
>
>
>
> _______________________________________________
> lpi-examdev mailing list
> lpi-examdev@lpi.org
> http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev



--
G. Matthew Rice <mr...@lpi.org>                         gpg id: EF9AAD20
_______________________________________________
lpi-examdev mailing list
lpi-examdev@lpi.org
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev

Reply via email to