You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by Roman Shtykh <rs...@yahoo.com.INVALID> on 2017/02/02 01:56:49 UTC
Plans for 4.0.0 release
Folks,
Any update on the plans for 4.0.0 release (JIRA says Jan 25th)?No rush, but if it is released this month, I would like to include RocketMQ and Ignite integration in the upcoming Apache Ignite 1.9 release. For this, we will have probably https://issues.apache.org/jira/browse/ROCKETMQ-76 be solved too.
Roman
Re: Plans for 4.0.0 release
Posted by chandresh pancholi <ch...@gmail.com>.
Recently we have release incubator-gossip first version.
Mentors also help you out with the release process.
Thanks
On Thu, Feb 2, 2017 at 2:48 PM, Willem Jiang <wi...@gmail.com> wrote:
> Is there any release candidate that we can take a look?
> From my experience, it's really hard to get the vote passed without any
> preview check.
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, Feb 2, 2017 at 11:39 AM, Xinyu Zhou <zh...@xinyu.im> wrote:
>
> > Hi,
> >
> > RocketMQ 4.0.0 is ready, and we will start calling a vote next week.
> >
> > Regards,
> > yukon
> >
> >
> > On Thu, Feb 02, 2017 at 9:57am, Roman Shtykh < rshtykh@yahoo.com.invalid
> > [rshtykh@yahoo.com.invalid] > wrote:
> > Folks,
> > Any update on the plans for 4.0.0 release (JIRA says Jan 25th)?No rush,
> > but if it is released this month, I would like to include RocketMQ and
> > Ignite integration in the upcoming Apache Ignite 1.9 release. For this,
> we
> > will have probably https://issues.apache.org/jira/browse/ROCKETMQ-76 be
> > solved too.
> > Roman
> >
>
--
Chandresh Pancholi
Senior Software Engineer
Flipkart.com
Email-id:chandresh.pancholi@flipkart.com
Contact:08951803660
Re: Plans for 4.0.0 release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Thanks for you input, I mistakenly believe that we must upload RC to Nexus
> before a vote, and now I have uploaded the 4.0.0-incubating RC to dist dir
You can put a snapshot up for voting on if you want [1], different PPMC /PMC do this slightly differently.
I prefer the dist/dev directory as it makes it easier for the IPMC to review and publish teh release to the official /dist area.
Thanks,
Justin
1. http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
Re: Plans for 4.0.0 release
Posted by yukon <yu...@apache.org>.
Hi Justin,
Thanks for you input, I mistakenly believe that we must upload RC to Nexus
before a vote, and now I have uploaded the 4.0.0-incubating RC to dist dir:
1.
https://dist.apache.org/repos/dist/dev/incubator/rocketmq/4.0.0-incubating/
The keys file:
2. https://dist.apache.org/repos/dist/dev/incubator/rocketmq/KEYS
We are performing a source-only release, please mentors help review it,
many thanks for that.
> I also notice that the current site may need a few changes to comply with
branding policy [2]. It is for example missing a incubating disclaimer so
it's not obvious that this in an incubating project.
We will fix this issue soon.
Regards,
yukon
On Thu, Feb 2, 2017 at 8:15 PM, Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> > Thank you for reminding, the release candidate can’t upload to Nexus at
> the moment
>
> Nexus is not the primary location for a RC it need to be uploaded to [1
> before a vote is caled]. If someone can point me to what is going to be
> released I can check it before a vote is called
>
> I also notice that the current site may need a few changes to comply with
> branding policy [2]. It is for example missing a incubating disclaimer so
> it's not obvious that this in an incubating project.
>
> Having a prominent link to GitHub is also not following policy. [3]
>
> As the project is incubating it’s not expected that it gets everything
> correct right away so there’s no issues with any of the above as long as
> they are fixed before graduation.
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/dev/release-distribution#dist-dir
> 2. http://incubator.apache.org/guides/branding.html
> 3. http://www.apache.org/legal/release-policy.html#what
>
>
Re: Plans for 4.0.0 release
Posted by yukon <yu...@apache.org>.
@Willem, My maven setup is seems ok, but the upload request was forbade by
Nexus, I think it should be a permission issue, and use AWS box as a
release host is really a great choice.
Regards,
yukon
On Thu, Feb 2, 2017 at 9:11 PM, Willem Jiang <wi...@gmail.com> wrote:
> @Justin
> We(Apache Camel) use the nexus stage repo for release candidate
> verification, as the end user may use maven to download the artifact jars
> instead of just use the zip artifacts.
>
> As the Apache release distribution directory are synced which other mirrors
> site, it could confuse the user when we just replace the new released
> artifacts with the old one.
>
> @yukon
> Please take a look at the release guide[1], you may need to do some setup
> on your computer first to upload the artifacts to the nexus.
> For my Camel release experience, it could be better if you use AWS box
> instead of your own computer for better network connection (which is not
> blocked by the Great Fire Wall)
>
> [1]http://camel.apache.org/release-guide.html
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, Feb 2, 2017 at 8:15 PM, Justin Mclean <ju...@classsoftware.com>
> wrote:
>
> > Hi,
> >
> > > Thank you for reminding, the release candidate can’t upload to Nexus at
> > the moment
> >
> > Nexus is not the primary location for a RC it need to be uploaded to [1
> > before a vote is caled]. If someone can point me to what is going to be
> > released I can check it before a vote is called
> >
> > I also notice that the current site may need a few changes to comply with
> > branding policy [2]. It is for example missing a incubating disclaimer so
> > it's not obvious that this in an incubating project.
> >
> > Having a prominent link to GitHub is also not following policy. [3]
> >
> > As the project is incubating it’s not expected that it gets everything
> > correct right away so there’s no issues with any of the above as long as
> > they are fixed before graduation.
> >
> > Thanks,
> > Justin
> >
> > 1. http://www.apache.org/dev/release-distribution#dist-dir
> > 2. http://incubator.apache.org/guides/branding.html
> > 3. http://www.apache.org/legal/release-policy.html#what
> >
> >
>
Re: Plans for 4.0.0 release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> @Justin
> We(Apache Camel) use the nexus stage repo for release candidate
> verification, as the end user may use maven to download the artifact jars
> instead of just use the zip artifacts.
Maven isn’t an offical realise area [1] (even if that where most people end up getting the software from) IMO best practice is to place the RC in the dev area and then when releasing do a svn move [2] to release then and then separately publish to maven.
> As the Apache release distribution directory are synced which other mirrors site.
The dev area is not mirrored.
Thanks,
Justin
1 http://www.apache.org/legal/release-policy#where-do-releases-go
2. http://www.apache.org/legal/release-policy.html#stage
Re: Plans for 4.0.0 release
Posted by Willem Jiang <wi...@gmail.com>.
@Justin
We(Apache Camel) use the nexus stage repo for release candidate
verification, as the end user may use maven to download the artifact jars
instead of just use the zip artifacts.
As the Apache release distribution directory are synced which other mirrors
site, it could confuse the user when we just replace the new released
artifacts with the old one.
@yukon
Please take a look at the release guide[1], you may need to do some setup
on your computer first to upload the artifacts to the nexus.
For my Camel release experience, it could be better if you use AWS box
instead of your own computer for better network connection (which is not
blocked by the Great Fire Wall)
[1]http://camel.apache.org/release-guide.html
Willem Jiang
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Thu, Feb 2, 2017 at 8:15 PM, Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> > Thank you for reminding, the release candidate can’t upload to Nexus at
> the moment
>
> Nexus is not the primary location for a RC it need to be uploaded to [1
> before a vote is caled]. If someone can point me to what is going to be
> released I can check it before a vote is called
>
> I also notice that the current site may need a few changes to comply with
> branding policy [2]. It is for example missing a incubating disclaimer so
> it's not obvious that this in an incubating project.
>
> Having a prominent link to GitHub is also not following policy. [3]
>
> As the project is incubating it’s not expected that it gets everything
> correct right away so there’s no issues with any of the above as long as
> they are fixed before graduation.
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/dev/release-distribution#dist-dir
> 2. http://incubator.apache.org/guides/branding.html
> 3. http://www.apache.org/legal/release-policy.html#what
>
>
Re: Plans for 4.0.0 release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Thank you for reminding, the release candidate can’t upload to Nexus at the moment
Nexus is not the primary location for a RC it need to be uploaded to [1 before a vote is caled]. If someone can point me to what is going to be released I can check it before a vote is called
I also notice that the current site may need a few changes to comply with branding policy [2]. It is for example missing a incubating disclaimer so it's not obvious that this in an incubating project.
Having a prominent link to GitHub is also not following policy. [3]
As the project is incubating it’s not expected that it gets everything correct right away so there’s no issues with any of the above as long as they are fixed before graduation.
Thanks,
Justin
1. http://www.apache.org/dev/release-distribution#dist-dir
2. http://incubator.apache.org/guides/branding.html
3. http://www.apache.org/legal/release-policy.html#what
Re: Plans for 4.0.0 release
Posted by Xinyu Zhou <zh...@xinyu.im>.
Hi Willem,
Thank you for reminding, the release candidate can’t upload to Nexus at the moment, and blocked by this issue https://issues.apache.org/jira/browse/INFRA-13373 [https://issues.apache.org/jira/browse/INFRA-13373] .
When the release candidate is ready, please mentors kindly help review it before calling a vote.
Regards, yukon
On Thu, Feb 2, 2017 at 5:18 PM, Willem Jiang <wi...@gmail.com> wrote:
Is there any release candidate that we can take a look?
From my experience, it's really hard to get the vote passed without any
preview check.
Willem Jiang
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Thu, Feb 2, 2017 at 11:39 AM, Xinyu Zhou <zh...@xinyu.im> wrote:
> Hi,
>
> RocketMQ 4.0.0 is ready, and we will start calling a vote next week.
>
> Regards,
> yukon
>
>
> On Thu, Feb 02, 2017 at 9:57am, Roman Shtykh < rshtykh@yahoo.com.invalid
> [rshtykh@yahoo.com.invalid] > wrote:
> Folks,
> Any update on the plans for 4.0.0 release (JIRA says Jan 25th)?No rush,
> but if it is released this month, I would like to include RocketMQ and
> Ignite integration in the upcoming Apache Ignite 1.9 release. For this, we
> will have probably https://issues.apache.org/jira/browse/ROCKETMQ-76 be
> solved too.
> Roman
>
Re: Plans for 4.0.0 release
Posted by Willem Jiang <wi...@gmail.com>.
Is there any release candidate that we can take a look?
From my experience, it's really hard to get the vote passed without any
preview check.
Willem Jiang
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Thu, Feb 2, 2017 at 11:39 AM, Xinyu Zhou <zh...@xinyu.im> wrote:
> Hi,
>
> RocketMQ 4.0.0 is ready, and we will start calling a vote next week.
>
> Regards,
> yukon
>
>
> On Thu, Feb 02, 2017 at 9:57am, Roman Shtykh < rshtykh@yahoo.com.invalid
> [rshtykh@yahoo.com.invalid] > wrote:
> Folks,
> Any update on the plans for 4.0.0 release (JIRA says Jan 25th)?No rush,
> but if it is released this month, I would like to include RocketMQ and
> Ignite integration in the upcoming Apache Ignite 1.9 release. For this, we
> will have probably https://issues.apache.org/jira/browse/ROCKETMQ-76 be
> solved too.
> Roman
>
Re: Plans for 4.0.0 release
Posted by Xinyu Zhou <zh...@xinyu.im>.
Hi,
RocketMQ 4.0.0 is ready, and we will start calling a vote next week.
Regards,
yukon
On Thu, Feb 02, 2017 at 9:57am, Roman Shtykh < rshtykh@yahoo.com.invalid
[rshtykh@yahoo.com.invalid] > wrote:
Folks,
Any update on the plans for 4.0.0 release (JIRA says Jan 25th)?No rush, but
if it is released this month, I would like to include RocketMQ and Ignite
integration in the upcoming Apache Ignite 1.9 release. For this, we will
have probably https://issues.apache.org/jira/browse/ROCKETMQ-76 be solved
too.
Roman