On 02/20/11 at 12:37pm, Thomas Zimmermann wrote: > Am Freitag 18 Februar 2011, 18:49:14 schrieb Simon Busch: > > My idea is now: Let use define some release cycle and release maybe at > > two times a year a new version of SHR/FSO which has features we define > > when we starting developing the new version. For example: Next release > > should be 2011.04. Now we define which machines should be supported by > > this release and which features we want to provide. This can be the Palm > > Pre / N900 device with basic Call support integrated in FSO and SHR. We > > define this as a feature of this release and work until 2011.04 to get > > this stable and usable for the user. All other features like SMS are not > > part of this release. If we can define such a release cycle we know > > everytime on what kind of features we are currently working.
> For SHR i've planned a release cycle of 2 releases per year. And i wanted to > release one at the beginning of the year, but there are some bugs in FSO that > i can't solve and wich prevent me from releasing it. > The plan is to base the releases on every second stable release of OE, so we > still have some time to finish SHR-testing2011.1 before OE-2011.6 :-) > For those interested in a release of SHR it would be nice if you can help me > to fix the bugs in the basic telephony support, then we can release testing. Ok, at this point we maybe have to specify which machine we want to target with a release. As of now we only have _stable_ support for the om-gta01/gta02 machines. All other machine are not finished and ready for daily use as the lack some features. In my opinion these should be part of a release but with a limited feature set. We have to get some plan of features we want to have for which machine in a release. Even we have to collect bugs we want to fix for a release. We can't target all known bugs at all, we have to feed them step by step. So for example the target for the first release maybe basic telephony support for a defined set of devices (maybe there is even support for more features for some devices but it's not supported as stable and ready for daily use). If we have done this in a first release we can go further and target more features with the next release. In the end we have to get a written plan for each release and have to assign responsibility to different persons who wants to participiate in a release. The who and what have to be set before we start working on a release, otherwise the possibility to not finish the release is very high ... regards, morphis _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
