Welcome, Guest. Please login or register. Did you miss your activation email?

Author Topic: Meaning of "High Priority" and "Low Priority&  (Read 5061 times)

0 Members and 2 Guests are viewing this topic.

quasius

  • Full Member
  • ***
  • Posts: 166
    • View Profile
Meaning of "High Priority" and "Low Priority&
« on: July 15, 2008, 03:07:52 am »
What do "High Priority" and "Low Priority" on the roadmap mean?  Is everything there scheduled for 1.4 or is the low priority for 1.5?  I though low priority meant not in next the version.  But I'd also thought I read render-to-image and per-drawable shaders would be in the next version, and they are listed as low priority.

Laurent

  • Administrator
  • Hero Member
  • *****
  • Posts: 32498
    • View Profile
    • SFML's website
    • Email
Meaning of "High Priority" and "Low Priority&
« Reply #1 on: July 15, 2008, 04:52:28 am »
Well, first of all it's just an indication. I do it on my free time and according to my motivation, so don't consider the roadmap as a schedule ;)

Low priority tasks are those which are less impotant, but also the big ones that I'm not sure I'll be able to implement for the next version.

So some low priority features may appear in 1.4, while some high priority tasks may not be completed until 1.5.
Laurent Gomila - SFML developer

 

anything