Hi Aurelien,

Right now I've got a window where I can crack on with reviewing and
merging submissions, but as you'll appreciate I've got a big backlog
to deal with so not having to jump through any additional hoops is
critical - using git right now while good in the long term is
additional hoops I could do with out.

Something that would help me as well is keeping individual submissions
on their own threads as it's relatively common for different
submissions have different merge paths and discussions.  Some
submissions are straight forward fixes that I can review and merge
within a five minute window and get quickly on to the next submissions
- these I'd classify as "low hanging fruit that are easy to pick",
while others require a great deal of research into the topic,
reproducing bugs and then quite a bit of discussion to come to the
final solution that is merged.  Having seperate threads make it easy
to keep track of the various individual topics - while pushing them
all together makes for a mess if any discussion is required.

So ideally for me could you post the full source code updates to the
representative original threads.  If you feel I've overlooked one of
them, but there doesn't need any update to the original source code
posted then feel free to post a "don't forget" me post, I don't mind
this - helps remind me that these individual submissions that are deep
in the my backlog of submissions is still required.

At this stage ordering of submissions isn't so critical to me - I just
need to get through them, so if there are particular submissions that
are critical to the community then I'm happy for the community to
shout loudest about them.

Robert.
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org

Reply via email to