Hi Dan,

No problem, MQTT and other IOs will be in the next release..

IMHO, it would be great to have:
1. A release reminder couple of days before a release. Just to ask everyone if there's no objection (something like this: https://lists.apache.org/thread.html/80de75df0115940ca402132338b221e5dd5f669fd1bf915cd95e15c3@%3Cdev.karaf.apache.org%3E) 2. A roughly release schedule on the website (something like this: http://karaf.apache.org/download.html#container-schedule for instance).

Just my $0.01 ;)

Regards
JB

On 10/20/2016 06:30 PM, Dan Halperin wrote:
Hi JB,

This is a great discussion to have! IMO, there's no special functionality
requirements for these pre-TLP releases. It's more important to make sure
we keep the process going. (I think we should start the release as soon as
possible, because it's been 2 months since the last one.)

If we hold a release a week for MQTT, we'll hold it another week for some
other new feature, and then hold it again for some other new feature.

Can you make a strong argument for why MQTT in particular should be release
blocking?

Dan

On Thu, Oct 20, 2016 at 9:26 AM, Jean-Baptiste Onofré <[email protected]>
wrote:

+1

Thanks Aljosha !!

Do you mind to wait the week end or Monday to start the release ? I would
like to include MqttIO if possible.

Thanks !
Regards
JB

⁣​

On Oct 20, 2016, 18:07, at 18:07, Dan Halperin <[email protected]>
wrote:
On Thu, Oct 20, 2016 at 12:37 AM, Aljoscha Krettek
<[email protected]>
wrote:

Hi,
thanks for taking the time and writing this extensive doc!

If no-one is against this I would like to be the release manager for
the
next (0.3.0-incubating) release. I would work with the guide and
update it
with anything that I learn along the way. Should I open a new thread
for
this or is it ok of nobody objects here?

Cheers,
Aljoscha


Spinning this out as a separate thread.

+1 -- Sounds great to me!

Dan

On Thu, Oct 20, 2016 at 12:37 AM, Aljoscha Krettek
<[email protected]>
wrote:

Hi,
thanks for taking the time and writing this extensive doc!

If no-one is against this I would like to be the release manager for
the
next (0.3.0-incubating) release. I would work with the guide and
update it
with anything that I learn along the way. Should I open a new thread
for
this or is it ok of nobody objects here?

Cheers,
Aljoscha

On Thu, 20 Oct 2016 at 07:10 Jean-Baptiste Onofré <[email protected]>
wrote:

Hi,

well done.

As already discussed, it looks good to me ;)

Regards
JB

On 10/20/2016 01:24 AM, Davor Bonaci wrote:
Hi everybody,
As a project, I think we should have a Release Guide to document
the
process, have consistent releases, on-board additional release
managers,
and generally share knowledge. It is also one of the project
graduation
guidelines.

Dan and I wrote a draft version, documenting the process we did
for the
first two releases. It is currently in a pull request [1]. I'd
invite
everyone interested to take a peek and comment, either on the
pull
request
itself or here on mailing list, as appropriate.

Thanks,
Davor

[1] https://github.com/apache/incubator-beam-site/pull/49


--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com





--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to