0.46 release plan proposal
Hi all,
Now that GSoC projects are finished and the code has had time to stabilize, it seems a good time to get the 0.46 release moving ahead. With Gutsy released, I finally have some time to contribute towards Inkscape release work, and will help try to get efforts organized.
I'd like to propose the following release plan, based roughly on the 0.45 plan. Let me know if there's anything missing.
1. Open development.
2. Chill. Development focuses on wrapping up. Identify 'make distcheck' issues Triage bug reports Run an About Screen contest First draft of Release Notes. Update tutorials and other docs
3. Frost. Most development complete. Release Notes should be >90% filled in. Bug Hunt: 500 points Post inkscape-0.46-alpha.tar.gz
4. Feature Freeze. No further development work. Disable features that can't be finished in time Focus on critical bug fixing. Finalize all tutorials, docs, etc. Finalize all extensions Translators create translations. Inkscape must pass 'make distcheck' Post inkscape-0.46-beta.tar.gz
5. Hard freeze. Only release wardens can commit to mainline. No further string changes Focus on release-critical bug fixing. Finalize translations, release notes, etc. Packagers test creating pkgs of the -beta release Post inkscape-0.46-rc1.tar.gz
6. Branch. Establish the Stable Branch for release Complete any late-late-late work. Final verification of packaging, release notes, docs, etc. Publish more release candidates until ready for release. Plan 0.46.1+ release(s), if needed
7. Release. Post inkscape-0.46.tar.gz Post packages Post official announcements
8. Open development.
I'm sort of thinking for this release we ought to plan on establishing a stable branch much earlier than we've done before, and maintain split devel / stable branches for a bit (maybe a couple months). I think that'd allow us to spend much more time than usual getting things release-worthy, without too heavily impacting people who wish to keep doing development work.
We'll have a bunch of interesting random tasks (mostly non-coding) to do to get the release polished up and ready to go. Are you interested in participating in the release team? Let me know!
Bryce
This looks nice, but what are you thinking for approximate dates?
--Ted
On Sat, 2007-11-03 at 10:56 -0700, Bryce Harrington wrote:
Hi all,
Now that GSoC projects are finished and the code has had time to stabilize, it seems a good time to get the 0.46 release moving ahead. With Gutsy released, I finally have some time to contribute towards Inkscape release work, and will help try to get efforts organized.
I'd like to propose the following release plan, based roughly on the 0.45 plan. Let me know if there's anything missing.
Open development.
Chill. Development focuses on wrapping up. Identify 'make distcheck' issues Triage bug reports Run an About Screen contest First draft of Release Notes. Update tutorials and other docs
Frost. Most development complete. Release Notes should be >90% filled in. Bug Hunt: 500 points Post inkscape-0.46-alpha.tar.gz
Feature Freeze. No further development work. Disable features that can't be finished in time Focus on critical bug fixing. Finalize all tutorials, docs, etc. Finalize all extensions Translators create translations. Inkscape must pass 'make distcheck' Post inkscape-0.46-beta.tar.gz
Hard freeze. Only release wardens can commit to mainline. No further string changes Focus on release-critical bug fixing. Finalize translations, release notes, etc. Packagers test creating pkgs of the -beta release Post inkscape-0.46-rc1.tar.gz
Branch. Establish the Stable Branch for release Complete any late-late-late work. Final verification of packaging, release notes, docs, etc. Publish more release candidates until ready for release. Plan 0.46.1+ release(s), if needed
Release. Post inkscape-0.46.tar.gz Post packages Post official announcements
Open development.
I'm sort of thinking for this release we ought to plan on establishing a stable branch much earlier than we've done before, and maintain split devel / stable branches for a bit (maybe a couple months). I think that'd allow us to spend much more time than usual getting things release-worthy, without too heavily impacting people who wish to keep doing development work.
We'll have a bunch of interesting random tasks (mostly non-coding) to do to get the release polished up and ready to go. Are you interested in participating in the release team? Let me know!
Bryce
This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
I wasn't. I expect it'll take us a couple months at least.
If everyone's cool with the plan, we could shoot for going into Chill a week or two from now, and see how things go from there.
Bryce
On Sat, Nov 03, 2007 at 02:51:46PM -0700, Ted Gould wrote:
This looks nice, but what are you thinking for approximate dates?
--TedOn Sat, 2007-11-03 at 10:56 -0700, Bryce Harrington wrote:
Hi all,
Now that GSoC projects are finished and the code has had time to stabilize, it seems a good time to get the 0.46 release moving ahead. With Gutsy released, I finally have some time to contribute towards Inkscape release work, and will help try to get efforts organized.
I'd like to propose the following release plan, based roughly on the 0.45 plan. Let me know if there's anything missing.
Open development.
Chill. Development focuses on wrapping up. Identify 'make distcheck' issues Triage bug reports Run an About Screen contest First draft of Release Notes. Update tutorials and other docs
Frost. Most development complete. Release Notes should be >90% filled in. Bug Hunt: 500 points Post inkscape-0.46-alpha.tar.gz
Feature Freeze. No further development work. Disable features that can't be finished in time Focus on critical bug fixing. Finalize all tutorials, docs, etc. Finalize all extensions Translators create translations. Inkscape must pass 'make distcheck' Post inkscape-0.46-beta.tar.gz
Hard freeze. Only release wardens can commit to mainline. No further string changes Focus on release-critical bug fixing. Finalize translations, release notes, etc. Packagers test creating pkgs of the -beta release Post inkscape-0.46-rc1.tar.gz
Branch. Establish the Stable Branch for release Complete any late-late-late work. Final verification of packaging, release notes, docs, etc. Publish more release candidates until ready for release. Plan 0.46.1+ release(s), if needed
Release. Post inkscape-0.46.tar.gz Post packages Post official announcements
Open development.
I'm sort of thinking for this release we ought to plan on establishing a stable branch much earlier than we've done before, and maintain split devel / stable branches for a bit (maybe a couple months). I think that'd allow us to spend much more time than usual getting things release-worthy, without too heavily impacting people who wish to keep doing development work.
We'll have a bunch of interesting random tasks (mostly non-coding) to do to get the release polished up and ready to go. Are you interested in participating in the release team? Let me know!
Bryce
This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Bryce Harrington wrote:
If everyone's cool with the plan, we could shoot for going into Chill a week or two from now, and see how things go from there.
I know for myself, being in grad courses right now, December was going to be a big time for me to work on refactoring my patch to be committed. If you guys want to chill before then, I suggest maybe checking in what I have done so far, and I can then check in the refactored version once it's done into the branch. I'd like to say that I could push to have it done sooner, but I know it's not realistic given the number of projects I have been working on.
Let me know what you guys think, Gail
On Sat, Nov 03, 2007 at 08:27:09PM -0400, Gail Carmichael wrote:
Bryce Harrington wrote:
If everyone's cool with the plan, we could shoot for going into Chill a week or two from now, and see how things go from there.
I know for myself, being in grad courses right now, December was going to be a big time for me to work on refactoring my patch to be committed. If you guys want to chill before then, I suggest maybe checking in what I have done so far, and I can then check in the refactored version once it's done into the branch. I'd like to say that I could push to have it done sooner, but I know it's not realistic given the number of projects I have been working on.
I'm fairly certain we'll be at Chill by December; I'm hoping this gives folks the holidays to squash bugs and do testing. So I'd say if you feel your patch is stable and something you definitely think needs to be in for 0.46, to get it in asap.
Also, could you also jot down some tips for things that'll be worth testing in it?
Bryce
Bryce Harrington wrote:
I'm fairly certain we'll be at Chill by December; I'm hoping this gives folks the holidays to squash bugs and do testing. So I'd say if you feel your patch is stable and something you definitely think needs to be in for 0.46, to get it in asap.
The patch is stable functionality-wise, but there are some code changes that will have to made whether the first version goes in or not. I know bulia was hoping to have the patch in for release, so perhaps he can pipe up on whether there is anything that needs to be addressed before that can happen (he made a bunch of comments in the patch tracker: http://sourceforge.net/tracker/?func=detail&aid=1778026&group_id=934...).
Also, could you also jot down some tips for things that'll be worth testing in it?
Hmm, well, I think this blog post should give the best idea on what was done: http://compscigail.blogspot.com/2007/08/summer-of-code-final-report.html
Gail
Bryce Harrington schrieb:
On Sat, Nov 03, 2007 at 08:27:09PM -0400, Gail Carmichael wrote:
Bryce Harrington wrote:
If everyone's cool with the plan, we could shoot for going into Chill a week or two from now, and see how things go from there.
I know for myself, being in grad courses right now, December was going to be a big time for me to work on refactoring my patch to be committed. If you guys want to chill before then, I suggest maybe checking in what I have done so far, and I can then check in the refactored version once it's done into the branch. I'd like to say that I could push to have it done sooner, but I know it's not realistic given the number of projects I have been working on.
I'm fairly certain we'll be at Chill by December; I'm hoping this gives folks the holidays to squash bugs and do testing. So I'd say if you feel your patch is stable and something you definitely think needs to be in for 0.46, to get it in asap.
I'm probably in a situation similar to Gail's right now. One of my four final examinations will be next Monday (Nov 12). I'm trying to get my loose ends (w.r.t. Inkscape :) ) tied up right now, but I won't be able to spend more than a few hours until then. Afterwards, the schedule is probably going to relax a bit (not much, though :( ) for two or three weeks so that I can try to get the major part of the reworked 3D box tool finished and checked in. Like Gail I was hoping to have until early December for this (I believe this tentative date was mentioned in an earlier post), but I really want to try to get it done even if Chill starts earlier.
It's hard to say if the time will be sufficient, but would you be willing to wait until the end of next week before announcing Chill? It should be clear by then if I can manage to bring my stuff in. Of course, only if it wouldn't mix up the entire schedule.
On the other hand, regarding your description ...
- Chill. Development focuses on wrapping up. Identify 'make distcheck' issues Triage bug reports Run an About Screen contest First draft of Release Notes. Update tutorials and other docs
... I'm wondering what precisely "Development focuses on wrapping up" means? Does it mean that there must not be any commits above a certain "size"? Or does it just mean that all developers should try to smooth out the existing stuff, eliminate bugs, etc. instead of implementing new features, but any code changes can still occur as required? I'm asking because in my case "wrapping up" does involve major changes (code-wise). This would result in one or more large commits. But except for some non-critical (mostly GUI-related) stuff it would only touch files I created myself, and since all the code is fairly orthogonal to the rest of the program, there shouldn't be a problem - if it doesn't work as intended or introduces too many bugs (in which case I would refrain from committing it in the first place :) ), it is simply excluded from the release branch later on. Or does something like this completely contradict the nature of Chill? Sorry for this probably dumb question but I'd like to know how much I need to hurry up if I want my stuff to hit this release.
Thanks, Max
On Wed, Nov 07, 2007 at 02:10:24AM +0100, Maximilian Albert wrote:
I'm probably in a situation similar to Gail's right now.
Unfortunately, it's hard to pick a time for release that is not inconvenient for at least a portion of the project. Since most of the time we allow development to proceed fairly free-form, when we do overlay a schedule, it's inevitable that some projects have to squeeze to fit.
It's hard to say if the time will be sufficient, but would you be willing to wait until the end of next week before announcing Chill? On the other hand, regarding your description ...
- Chill. Development focuses on wrapping up. Identify 'make distcheck' issues Triage bug reports Run an About Screen contest First draft of Release Notes. Update tutorials and other docs
... I'm wondering what precisely "Development focuses on wrapping up" means?
It's worded specifically for projects (presumably like yours and Gail's) that is nearing completion but needs to be given some additional time and got squeezed by the schedule imposition. We allocate some time to allow people to hurry those towards completion, while other developers shift focus to bugs. Of course, we take a risk here in that late development projects will have less QA time, but if we can get the QA work for completed development projects done early, in theory we'll have more QA attention to apply to the late development projects later on.
In any case, the main thing during Chill is that we need to avoid starting *new* projects.
I'm asking because in my case "wrapping up" does involve major changes (code-wise). This would result in one or more large commits. I'd like to know how much I need to hurry up if I want my stuff to hit this release. Thanks, Max
Right, it sounds like your project fits into the "wrapping up" clause. I think the most important thing that "wrapping up" projects should do, is to report status verbosely and frequently. Don't worry about the frequency or size of the commits - what you need to maximize is the *visibility* of what you're doing - especially any changes that you think have risk of adding bugs. Let us know how close you're getting, any blocking issues you run into, and highlight any areas where people could do things to help accelerate your progress.
Thanks, Bryce
Sounds like a good plan Bryce...yes, approx. timeline is good...holiday hacking is a good time for a release...
On Sat, 2007-11-03 at 10:56 -0700, Bryce Harrington wrote:
Hi all,
Now that GSoC projects are finished and the code has had time to stabilize, it seems a good time to get the 0.46 release moving ahead. With Gutsy released, I finally have some time to contribute towards Inkscape release work, and will help try to get efforts organized.
I'd like to propose the following release plan, based roughly on the 0.45 plan. Let me know if there's anything missing.
Open development.
Chill. Development focuses on wrapping up. Identify 'make distcheck' issues Triage bug reports Run an About Screen contest First draft of Release Notes. Update tutorials and other docs
Frost. Most development complete. Release Notes should be >90% filled in. Bug Hunt: 500 points Post inkscape-0.46-alpha.tar.gz
Feature Freeze. No further development work. Disable features that can't be finished in time Focus on critical bug fixing. Finalize all tutorials, docs, etc. Finalize all extensions Translators create translations. Inkscape must pass 'make distcheck' Post inkscape-0.46-beta.tar.gz
Hard freeze. Only release wardens can commit to mainline. No further string changes Focus on release-critical bug fixing. Finalize translations, release notes, etc. Packagers test creating pkgs of the -beta release Post inkscape-0.46-rc1.tar.gz
Branch. Establish the Stable Branch for release Complete any late-late-late work. Final verification of packaging, release notes, docs, etc. Publish more release candidates until ready for release. Plan 0.46.1+ release(s), if needed
Release. Post inkscape-0.46.tar.gz Post packages Post official announcements
I'll do my part on announcements, and more, but I'd like to help mentor for some others on this as well...Who would like to help me with this task? We can coordinate a major strike this time, with interviews, PR, press, etc...anyone?
Jon
- Open development.
I'm sort of thinking for this release we ought to plan on establishing a stable branch much earlier than we've done before, and maintain split devel / stable branches for a bit (maybe a couple months). I think that'd allow us to spend much more time than usual getting things release-worthy, without too heavily impacting people who wish to keep doing development work.
We'll have a bunch of interesting random tasks (mostly non-coding) to do to get the release polished up and ready to go. Are you interested in participating in the release team? Let me know!
Bryce
This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 11/4/07, Jon Phillips wrote:
I'll do my part on announcements, and more, but I'd like to help mentor for some others on this as well...Who would like to help me with this task? We can coordinate a major strike this time, with interviews, PR, press, etc...anyone?
I've done several interviews (Scribus, Tango, and another one is coming) before. Let me know if you need me here ;-)
Alexandre
On Sun, 2007-11-04 at 02:21 +0300, Alexandre Prokoudine wrote:
On 11/4/07, Jon Phillips wrote:
I'll do my part on announcements, and more, but I'd like to help mentor for some others on this as well...Who would like to help me with this task? We can coordinate a major strike this time, with interviews, PR, press, etc...anyone?
I've done several interviews (Scribus, Tango, and another one is coming) before. Let me know if you need me here ;-)
Alexandre
Please add yourself to the page for doing interviews, etc:
http://wiki.inkscape.org/wiki/index.php/AnnouncePlanning046
Jon
This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 11/5/07, Jon Phillips wrote:
Please add yourself to the page for doing interviews, etc:
OK, created a Tasks section there and added myself
Alexandre
On 11/4/07, Jon Phillips <jon@...235...> wrote:
I'll do my part on announcements, and more, but I'd like to help mentor for some others on this as well...Who would like to help me with this task? We can coordinate a major strike this time, with interviews, PR, press, etc...anyone?
I'll put my hand up to help with announcements and some of the PR stuff... I reckon a major hit of PR is needed, cos it is going to be a major release (feature-wise anyways...)
cheers,
ryanlerch
On Sun, Nov 04, 2007 at 02:46:31PM +1000, ryan lerch wrote:
On 11/4/07, Jon Phillips <jon@...235...> wrote:
I'll do my part on announcements, and more, but I'd like to help mentor for some others on this as well...Who would like to help me with this task? We can coordinate a major strike this time, with interviews, PR, press, etc...anyone?
I'll put my hand up to help with announcements and some of the PR stuff... I reckon a major hit of PR is needed, cos it is going to be a major release (feature-wise anyways...)
Cool, that'll be a huge help.
I think from a PR standpoint we need to be able to express what the top new feature(s) are in one sentence... one paragraph... and one page. Want to take a shot at writing these?
Bryce
On Sat, 2007-11-03 at 22:01 -0700, Bryce Harrington wrote:
On Sun, Nov 04, 2007 at 02:46:31PM +1000, ryan lerch wrote:
On 11/4/07, Jon Phillips <jon@...235...> wrote:
I'll do my part on announcements, and more, but I'd like to help mentor for some others on this as well...Who would like to help me with this task? We can coordinate a major strike this time, with interviews, PR, press, etc...anyone?
I'll put my hand up to help with announcements and some of the PR stuff... I reckon a major hit of PR is needed, cos it is going to be a major release (feature-wise anyways...)
Cool, that'll be a huge help.
I think from a PR standpoint we need to be able to express what the top new feature(s) are in one sentence... one paragraph... and one page. Want to take a shot at writing these?
Bryce
Awesome Ryan, yes take a first pass at what Bryce recommends and ping, and I'll take a pass...
Jon
Jon Phillips wrote:
On Sat, 2007-11-03 at 22:01 -0700, Bryce Harrington wrote:
On Sun, Nov 04, 2007 at 02:46:31PM +1000, ryan lerch wrote:
On 11/4/07, Jon Phillips <jon@...235...> wrote:
I'll do my part on announcements, and more, but I'd like to help mentor for some others on this as well...Who would like to help me with this task? We can coordinate a major strike this time, with interviews, PR, press, etc...anyone?
I'll put my hand up to help with announcements and some of the PR stuff... I reckon a major hit of PR is needed, cos it is going to be a major release (feature-wise anyways...)
Cool, that'll be a huge help.
I think from a PR standpoint we need to be able to express what the top new feature(s) are in one sentence... one paragraph... and one page. Want to take a shot at writing these?
Bryce
Awesome Ryan, yes take a first pass at what Bryce recommends and ping, and I'll take a pass...
Jon
Okies...
I am fleshing out the 0.46 release plan at the moment on the wiki, then i will have a go at the one sentence, paragraph and page feature overviews...
cheers,
ryanlerch
Please add one month to the release schedule. I want some time to contribute to 0.46, too. I have been too busy worrying about dependencies.
(ishmal) bob
On Sun, Nov 04, 2007 at 02:46:31PM +1000, ryan lerch wrote:
On 11/4/07, Jon Phillips <jon@...235...> wrote:
I'll do my part on announcements, and more, but I'd like to help mentor for some others on this as well...Who would like to help me with this task? We can coordinate a major strike this time, with interviews, PR, press, etc...anyone?
I'll put my hand up to help with announcements and some of the PR stuff... I reckon a major hit of PR is needed, cos it is going to be a major release (feature-wise anyways...)
Rejon and Ryan, can you give us a report on where we stand for PR, and what's planned to get done for the Chill phase?
Thanks, Bryce
A few people have had questions about undertaking new development projects at this stage.
In general, use your own judgement. New code that has a high risk of causing regressions probably should wait until after we branch. Small changes, or ones with small chance of regression may be okay.
In any case, if you do make significant changes, please post some advice/tips for testing the code. That will make it easier for others to help with validation. Also remember to update the Release Notes!
Bryce
On Sat, Nov 03, 2007 at 10:56:46AM -0700, Bryce Harrington wrote:
Hi all,
Now that GSoC projects are finished and the code has had time to stabilize, it seems a good time to get the 0.46 release moving ahead. With Gutsy released, I finally have some time to contribute towards Inkscape release work, and will help try to get efforts organized.
I'd like to propose the following release plan, based roughly on the 0.45 plan. Let me know if there's anything missing.
Open development.
Chill. Development focuses on wrapping up. Identify 'make distcheck' issues Triage bug reports Run an About Screen contest First draft of Release Notes. Update tutorials and other docs
Frost. Most development complete. Release Notes should be >90% filled in. Bug Hunt: 500 points Post inkscape-0.46-alpha.tar.gz
Feature Freeze. No further development work. Disable features that can't be finished in time Focus on critical bug fixing. Finalize all tutorials, docs, etc. Finalize all extensions Translators create translations. Inkscape must pass 'make distcheck' Post inkscape-0.46-beta.tar.gz
Hard freeze. Only release wardens can commit to mainline. No further string changes Focus on release-critical bug fixing. Finalize translations, release notes, etc. Packagers test creating pkgs of the -beta release Post inkscape-0.46-rc1.tar.gz
Branch. Establish the Stable Branch for release Complete any late-late-late work. Final verification of packaging, release notes, docs, etc. Publish more release candidates until ready for release. Plan 0.46.1+ release(s), if needed
Release. Post inkscape-0.46.tar.gz Post packages Post official announcements
Open development.
I'm sort of thinking for this release we ought to plan on establishing a stable branch much earlier than we've done before, and maintain split devel / stable branches for a bit (maybe a couple months). I think that'd allow us to spend much more time than usual getting things release-worthy, without too heavily impacting people who wish to keep doing development work.
We'll have a bunch of interesting random tasks (mostly non-coding) to do to get the release polished up and ready to go. Are you interested in participating in the release team? Let me know!
Bryce
well i cannot say a lot about core developpment, but on finalizing docs, the user_manual doc team is reaching to be ready for a kind of rewrite and i'm not sure if it could be done so early. As always, we'll do our best.
For official announcements, i could try to do some french announcement if none is already on the way. I've already alked about it with bryce, but to do this i'd need to get the official text some days befor so taht i can translate it and prepare a list.
pygmee
Feature Freeze. No further development work. Disable features that can't be finished in time Focus on critical bug fixing. Finalize all tutorials, docs, etc. Finalize all extensions Translators create translations. Inkscape must pass 'make distcheck'
Release. Post inkscape-0.46.tar.gz Post packages Post official announcements
Open development.
On Tue, Nov 06, 2007 at 10:32:58PM +0000, radar.map35@...8... wrote:
well i cannot say a lot about core developpment, but on finalizing docs, the user_manual doc team is reaching to be ready for a kind of rewrite and i'm not sure if it could be done so early. As always, we'll do our best.
The user_manual is a separate deliverable, right? If this is the case, then please feel free to order your schedule and development plans as makes the most sense for you. I also don't think we'd necessarily need to synchronize the release dates of the program and docs, although it would be nice if they were.
Assuming it's a separate deliverable, could you take the task of proposing a schedule for it (and mentioning any points at which we need to synchronize with the inkscape program)?
For official announcements, i could try to do some french announcement if none is already on the way. I've already alked about it with bryce, but to do this i'd need to get the official text some days befor so taht i can translate it and prepare a list.
Sure, in fact there has been some discussion on release announcements and translations - see rejon and other's posts on this. I think again this time we'll have a release team to coordinate the announcements and translations.
Bryce
participants (10)
-
Alexandre Prokoudine -
Bob Jamison -
Bryce Harrington -
Gail Carmichael -
Jon Phillips -
Maximilian Albert -
radar.map35＠...8... -
ryan lerch -
Ryan Lerch
-
Ted Gould