[Springpython-developer] Spring Python - updates regarding web site

[<gre...@mi...>]

Spring Python users,

Important information regarding updates to processes, web sites, etc.

1. I am trying to update http://springpython.webfactional.com when I can, so people can track what we are doing while migrating things to our new web space at SpringSource.

2. The trac site is still working, however, the "Browse Source" link takes you into the OLD repository. To view current, and up-and-coming changes, visit https://fisheye.springframework.org/browse/se-springpython-py. This is a viewer.

3. To actually check out a copy of the code, try https://src.springframework.org/svn/se-springpython-py/.

4. Currently, Spring Python is one project in the trunk called "springpython". The idea is that down the road, should we extend Spring Python with other projects, they can be put alongside "springpython" with their own svn space.

5. All the tickets have been migrated to JIRA, and thanks to a little effort, I got them in with the same ticket number. There are new tickets being created. Right now, Spring Python's ticket space is closed to anonymous readers. I can't immediately answer the question of SpringSource's policy on accounts. I also don't know the policy of when this would be made public. Stand by for updates.

6. Spring Python now has a dedicated forum at http://forum.springframework.org/forumdisplay.php?f=45. Go there to track current events. While I make updates from time-to-time at the trac site, the forums are where things are getting kicked around (if not through direct email). I suggest you go there if you want the latest info on what is happening, or if you have questions/comments.

7. SpringSource is working on setting up some wiki space for Spring Python. As soon as that is available, I will start migrating the wiki pages from the trac site over there.

8. Upcoming releases: 0.6 is the next targeted release, and it is currently scheduled for the end of August. We are focused on getting Spring Python working inside SpringSource's continuous integration server, and are making changes as needed to get this working. This will also be the release with SpringSource's official branding. Our chief focus on release 0.6 is quality, and you can't have quality until you start measuring things. This week, I did a test run and also saw overall test coverage of 85%. Hopefully, these stats will be releasable soon through CI, allowing you to also follow the quality assurance of Spring Python.

9. I want to publicly thank Sylvain, who is currently helping me migrate Spring Python sample apps from CherryPy 2 to CherryPy 3. He has been providing good feedback on the current state of affairs while reviewing the code written so far. I also wish to thank Russ, my SpringSource sponsor, who is doing the leg work to get me setup in SpringSource's server space, and also gives me SpringSource's viewpoint on things. Other people on this list have communicated with me in the past about specific issues or interests, and helped to make this a better product. I appreciate all feedback, positive or negative, and will continue to do so in the future.

Stay tuned,
Greg