04-05-2010, 04:54 PM
Omdat we op het moment een regeling hebben mbt wekelijkse update moeten we met een updated voorstle komen naar het Core-man.
Due to the starting of our new big version we want to change some things in our current update-cycle. Currently we release a new version weekly, together with a blogpost. As we will start developing a new version which will take a few months of developing time, we would like to reduce our current update-cycle. We propose a 2-weekly-update with bugfixes for all reported bugs as far as we can fix them. We will also merge these fixes with the new large version. This 2-weekly update will be accompanied by a blogpost, which talks about the fixed bugs, and gives more information about a feature that has been developed for 2.92 (or whatever we'll number the new version, we still gotta decide that), and 2 screenshots added. We propose this because it will cost us extra valuable time if we have to add stuff and update on a weekly base, while we can better spend that time on 2.92.
Due to the starting of our new big version we want to change some things in our current update-cycle. Currently we release a new version weekly, together with a blogpost. As we will start developing a new version which will take a few months of developing time, we would like to reduce our current update-cycle. We propose a 2-weekly-update with bugfixes for all reported bugs as far as we can fix them. We will also merge these fixes with the new large version. This 2-weekly update will be accompanied by a blogpost, which talks about the fixed bugs, and gives more information about a feature that has been developed for 2.92 (or whatever we'll number the new version, we still gotta decide that), and 2 screenshots added. We propose this because it will cost us extra valuable time if we have to add stuff and update on a weekly base, while we can better spend that time on 2.92.