Sorry if you misunderstood. I did mean monthly. The part where I mentioned a couple weeks was the longest I'd personally be willing to wait after releasing a "final" version before putting together a bugfix for it with whatever bugs there are. I was completely ignoring (had forgotten, actually) the monthly thing by that point. Actually, it might fit well - release the big new version on the month in place of the normal monthly bugfix. Then half a month later (two weeks) do a bugfix. Then another two weeks for the next bugfix, which would put things back on the monthly schedule again, and ensure that big releases get some fixes in faster.I suggested once a month release a bug fix version, Pizzasgood suggested every 2.5 weeks or something, I think thats a bit too many releases in the year.
As for your concern about Git vs. testers - Git is for the developers, not testers. The testers could just ignore it if they didn't like Git. There is no reason we couldn't release normal isos for the uninitiated to test with. Alpha/beta/rc releases would still happen normally. Git would provide people with an additional option, to avoid the need to wait for alphas. But it's mainly to help simplify the development.
I am feeling like Git is getting ahead of me though. I had intended to start working on Pizzapup using Git before we use it with Puppy, so that I could have a better idea of how practical it will be and what-not, to avoid wasting people's time if it flops. But I've been swamped since February. I've had an average of 12-14 hour weekdays and 7 hour Saturdays. School is finally wrapping up for summer though, so I can get some work in soon.
Also, if we intend to replace Unleashed with Woof in the near future, then we may as well just keep doing Puppy the old way until then.