Forum OpenACS Development: Re: 6.0 Release Schedule Proposal

Collapse
Posted by marc spitzer on
I like the major/minor idea.  Where a major release may include any of the following:

1: need to upgrade db
2: need to upgrade aol server, not including minor/security patches
3: major changes in the db scheema
4: major changes to the api's, not including new apis
5: at least once a year, just to keep the ball rolling

I hate suprises, 4 to 5 work, 5 to 6 not much work, 6 to 7 not much work, etc.  How do I quickly tell the difference and explain it to management/customers?  If on the other hand I can point to 5.x to 6.x(bigger job) vs 5.x to 5.y it makes life easier.