Here's the status after today's work. Hopefully it's enough to make an alpha-1
release? I agree with the release early and often:
- Sphinx documentation is in place. Thanks Txema. It produces one error
on Mac related to pyglet.com which is Windows only. Epydoc is remove and Sphinx
is in the tools/ folder. Run it from the pyglet folder with:
./make.py docs
- Deleted about 15 really old issues. I added comments to the authors
thanking them for the issue, saying we are closing it because it is so old and
we need to cleanup the list, and asking them to repost the issue if it's still
around. I had hoped to bring the number of issues to less than 100 so they are
all on one page. Didn't quite make it: 103.
- Applied a small handful of patches, mostly documentation change
requests.
Didn't get to any test failures or testing output.
Regarding collating test output, my thoughts:
- Use google forms to collect data into a google docs spreadsheet.
- Form would include:
- Date
- platform information, python bit size, version, etc
- pyglet version
- OpenGL info dump
- hg id if any. I.e. handle the case where people are running
from tarball
- # tests run
- # tests failed
- list of failures - try to make it short and readable
- complete test output
- Modify tests.py so at the end, it asks the user if we may upload
their test results. If so, submit via HTTP post.
On Jun 21, 2012, at 5:58 PM, Richard Jones wrote:
> On 22 June 2012 10:32, Winston Wolff <[email protected]> wrote:
>> I'm going to spend another day tomorrow working on the release. My to do
>> list is:
>>
>> - apply Txema's work on documentation
>> - apply patch in issue 580 from M Paola for DDS_RGBA_DXT1_LOAD test failures
>> - go through issues to see if there are other patches that look useful and
>> safe (I don't want to add too much which might delay this release)
>> - try to fix other test failures
>
> Awesome, thanks! I'm sorry I've been so quiet this week. I think after
> applying the few fixes that've come up during testing we should push
> out the release, with the intention of releasing the alpha "early" and
> releasing fixes often.
>
>
>> - improve output format of test runner so we can get better data on how
>> Pyglet is working.
>
> Just some thoughts on this. Pie in the sky stuff. It would be useful
> if this could include some thinking about what to do with test
> reports. Having people email the mailing list - or even creating
> individual issue tracker items - mostly generates noise. If the test
> run output could be generated in a structured manner we could feed it
> into a collation system (which wouldn't take a significant effort to
> develop.) The run output would need to include the OpenGL info dump,
> repository version and testing log. The testing log would ideally be
> able to be captured over multiple partial runs to allow for complete
> system failures in individual tests.
>
> I'd be happy to install a web service to collate the above information
> if someone were to write it. Doesn't have to be fancy. If no-one steps
> up I'll try to write something myself. If we do get something done
> it'd be good to have from the earliest alpha releases.
>
>
> Richard
>
> --
> You received this message because you are subscribed to the Google Groups
> "pyglet-users" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/pyglet-users?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyglet-users?hl=en.
