Hello,
we noticed that several new reviews are about to get in Tizen 3 relative
to 2.3 API.
see as example (not a complete list) ;
https://review.tizen.org/gerrit/33153
https://review.tizen.org/gerrit/33151
https://review.tizen.org/gerrit/33150
https://review.tizen.org/gerrit/33111
https://review.tizen.org/gerrit/33110
While I have no principle issue against such action, I would like to see
a few action taken in order to ensure that Tizen 3 consistency is kept :
- a Jira Ticket should be open for each change required. In order to
get a full visibility of the change to come rather than to see them
commit by commit.
Preferably we should add a label to each ticket to ease filtering
(e.g. "2.3 compatibility").
Developper should mark the Jira ticket as released when his come is
merged, so that QA know that they can test it. QA should close it when
verified.
The model use to align with Yocto can be taken as example.
The goal here is to allow a global visibility on all the change to come.
I would also like to see a clear pointer toward the test cases to be
used by QA to test those new features and a communication on the mailing
list giving the list of the packages to be affected in order to warn all
developers of the change to come.
Thanks.
--
Dominig ar Foll
Senior Software Architect
Open Source Technology Centre
Intel SSG
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
