[21:10] <@sk89q> I am going to rollback the change to remove P2/P3
[21:11] <@sk89q> 6 months is nothing when you have things to do in real life
[21:11] <famerdave> the plugin still works - and people still use it
[21:11] <famerdave> why not let them continue
[21:13] * Afforess is now known as Afforess|Away
[21:13] <@sk89q> unless there is another reason of course, like poor detection of the right permissions plugin
[21:13] <@zml2008> P3 has been known to cause server crashes
[21:14] <@zml2008> but whatever, the removal of the old events system and configuration system will kill it soon enough
[21:14] <@sk89q> when that happens, then it can be removed
[21:14] <famerdave> you don't think someone will update it for the new systems?
[21:15] <@sk89q> and seemingly as though 1 week is 'a lot of time' for bukkit folk, it will be removed soon, so what's the worry?
[21:15] <@sk89q> it's also not JUST p2/p3 -- it's a particular API
[21:18] <@zml2008> A long-deprecated API
[21:19] <@sk89q> deprecation of software tends to go for years
[21:19] <@zml2008> Bukkit's been around for 1 year
[21:20] <@sk89q> it has had a very troublesome history with permissions and p2/p3 lasted for the majority of the time
[21:20] <@sk89q> the length of time of deprecation is also not related to the length of service
[21:21] <@sk89q> by completely killing something, you are imposing your deprecation issue more important than others
[21:21] <famerdave> And people use P2/P3 still, if someone is using something a lot, it normally takes YEARS to depracate
[21:21] <@sk89q> and for all we know a lot of people play MC on the side, so they don't stay current with events
[21:22] <@sk89q> maintaining the permissions API is exceptionally simple
[21:22] <@sk89q> it rarely requires changes and yet removing causes a potentially high amount of headache for an unknown number of people

[edited for spelling, line merges]