On 28/07/2014 14:37, [email protected] wrote:
On , Philippe Coval wrote:
Hi
I used to maintain elementary,
(we did not followed upstream during ivi release)
https://panel.tizen.org/app/packagedb/gittrees/1510/
https://panel.tizen.org/app/packagedb/subdomains/45/
If there is a reason to upgrade it,
please file a bug an assign it to me (pcoval)
If you want to help on this you can still push to sandbox/$user/devel
branch
I'll see what I can do with that...
Sorry for late reply... I know it's frustrating when you're "blocked" by
maintainers
so create request bug is the good way to get their attention
Regards
Hello,
I didn't know these links yet. I only check the maintainer list in
the gerrit review sites.
Actually I am planning to upgrade upstream branch for EFL in the tizen
daily (or weekly)
Unsure this the way we want to maintain tizen:common since we want it to
be a minimum stable
to offer a reliable base for other profiles..
because tizen upstream branch didn't synced well with upstream
opensource EFL.
As said earlier if there is a reason to upgrade EFL, please request a
merge sync on jira
and details the benefits to upgrading it
then I'll be happy to helping the maintainance job
we just want it to be tracked (using Bug-Tizen: in commit messages)
There are some tizen only patches into upstream branch in the efl,
elementary.
Those patches should be upstreamed if not please file a bug
IMHO, upstream branch should be synced with opensource upstream
because Tizen:common project is used for common.
then if a profile want a newer version to be integrated just request it
If anyone working with specific project (e.g. Mobile, IVI), I think
that they should make patch only for their branch (e.g. profile/mobile
or profile/ivi)
ok with that
But If I should make a bug request for upstream sync daily, that seems
to be weird.
what about doing this on proper release ?
I don't know you can do that for upstream branch daily.
I used to do that automatically by creating snapshots
of some upstream projects
but i am unsure they will be built into regular repos
This needs to be discussed.
Yes please file a bug , there is no reason to not enhance coop model
between upstream
and doing this on jira will be better than on mailing lists since it
does affect a few of subscribers
I'll do my best to satisfy all
Regards
--
mailto:[email protected] -- gpg:0x467094BC
xmpp:[email protected]
https://dockr.eurogiciel.fr/blogs/embedded/author/pcl/
.
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
