Hi Tixy
On 10/04/2012 12:55 PM, Jon Medhurst (Tixy) wrote:
Hi Andrey
Now I'm providing a single LT topic based off linux-linaro-core-tracking
(llct), and you said that you need everyone to base off the same version
of llct,
Yes, this is currently the case.
don't we need some kind of notification system where you
announce a plan to rebuild linux-linaro and give us a version of llct to
base our LT branches off?
Yes, this makes sense.
Would the following plan be OK:
(<N> should normally be 0, but may be a small positive number)
* till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
* October 9: ll rebuild based on llct-20121005.<N>
* October 16: ll rebuild based on llct-20121012.<N>
* October 23: ll rebuild based on llct-20121019.<N>, ll code freeze (no
massive ll topics updates after that; bugfixes only)
ll and llct could be updated between these dates as well, but without
changes in the "normal" ll topics - just my "last-time-fixes" pseudo
topics could change.
Also I believe that the ll topics could actually based on *any* recent
enough llct version. But I want to double check the pro's and contra's
before making this statement official.
What concerns me now are the ll topics based on ll itself (just one real
topic atm: ste-lt-next). Would it be a problem for any of the topic
maintainers if I request all the ll topics to be based on llct, on
another ll topic (I must be told about that), even on vM.N-rcX
kernel.org tag if this is good for the topic maintainer, but not on ll
itself?
Thanks,
Andrey
PS
The multiplatform topic is removed from llct starting from llct-20120924.0
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
