From: Juergen Gross <jgross@suse.com>
To: Roman Shaposhnik <roman@zededa.com>
Cc: luwei.kang@intel.com, "Wei Liu" <wl@xen.org>,
konrad.wilk@oracle.com,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Marek Marczykowski" <marmarek@invisiblethingslab.com>,
olekstysh@gmail.com, "Paul Durrant" <paul.durrant@citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
puwen@hygon.cn, xen-devel@lists.xenproject.org,
chao.gao@intel.com, Volodymyr_Babchuk@epam.com,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [ANNOUNCE] Xen 4.13 Development Update
Date: Thu, 12 Sep 2019 08:36:04 +0200 [thread overview]
Message-ID: <d5975dd9-250f-5e8e-e3b2-3728cf652449@suse.com> (raw)
In-Reply-To: <CAMmSBy_huA=jDwwGfzN1cB8zt3DNP5iJZNSQ_doe1RK-4kzw8Q@mail.gmail.com>
On 12.09.19 08:10, Roman Shaposhnik wrote:
> Hi!
>
> On Fri, Sep 6, 2019 at 12:41 AM Juergen Gross <jgross@suse.com> wrote:
>>
>> This email only tracks big items for xen.git tree. Please reply for items you
>> would like to see in 4.13 so that people have an idea what is going on and
>> prioritise accordingly.
>>
>> You're welcome to provide description and use cases of the feature you're
>> working on.
>>
>> = Timeline =
>>
>> We now adopt a fixed cut-off date scheme. We will release about every 8 months.
>> The upcoming 4.13 timeline are as followed:
>>
>> * Last posting date: September 13th, 2019
>
> Naive question perhaps, but since the first deadline is two days away,
> I'm wondering
> what's my best option to provide early feedback? Currently we're testing with
> master branch in Project EVE, but I've noticed that it is 4 weeks behind staging
> at this point.
>
> When is it expected to catch up?
As soon as OSStest is succeeding on staging.
Any feedback is very welcome, of course. In case you could base your
tests on staging this might speed up things, depending on your tests
(failing for the same reasons as OSStest wouldn't add that much
information, but finding other bugs would be a big plus).
In the RC-phase master should be rather close to staging, as a new RC
is always tagged on the master branch and staging should receive fixes
only (there are some exceptions from time to time, like security fixes).
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-09-12 6:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 7:40 [Xen-devel] [ANNOUNCE] Xen 4.13 Development Update Juergen Gross
2019-09-06 16:13 ` Andrew Cooper
2019-09-06 16:32 ` Konrad Rzeszutek Wilk
2019-09-09 7:52 ` Paul Durrant
2019-09-12 5:46 ` Chao Gao
2019-09-12 6:10 ` Roman Shaposhnik
2019-09-12 6:36 ` Juergen Gross [this message]
2019-09-13 16:19 ` Oleksandr
-- strict thread matches above, loose matches on Subject: below --
2019-09-28 5:09 Juergen Gross
2019-09-28 14:07 ` Steven Haigh
2019-08-01 16:00 Juergen Gross
2019-08-01 16:47 ` Andrew Cooper
2019-08-02 8:50 ` Wei Liu
2019-08-01 18:11 ` Roman Shaposhnik
2019-08-02 9:04 ` Roger Pau Monné
2019-08-02 9:57 ` Dario Faggioli
2019-08-02 15:52 ` Anthony PERARD
2019-08-02 17:07 ` Oleksandr
2019-08-12 10:02 ` Paul Durrant
2019-07-01 11:35 Juergen Gross
2019-07-01 11:42 ` Jan Beulich
2019-07-01 12:09 ` Juergen Gross
2019-07-01 17:24 ` Volodymyr Babchuk
2019-05-28 10:54 Juergen Gross
2019-05-28 10:54 ` [Xen-devel] " Juergen Gross
2019-05-28 13:44 ` Tamas K Lengyel
2019-05-28 13:44 ` [Xen-devel] " Tamas K Lengyel
2019-05-28 23:07 ` Andrew Cooper
2019-05-28 23:07 ` [Xen-devel] " Andrew Cooper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5975dd9-250f-5e8e-e3b2-3728cf652449@suse.com \
--to=jgross@suse.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=chao.gao@intel.com \
--cc=jbeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=luwei.kang@intel.com \
--cc=marmarek@invisiblethingslab.com \
--cc=olekstysh@gmail.com \
--cc=paul.durrant@citrix.com \
--cc=puwen@hygon.cn \
--cc=roger.pau@citrix.com \
--cc=roman@zededa.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).