ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Ozerov <voze...@gridgain.com>
Subject Re: Apache Ignite 2.7 - Release Procedure issues
Date Thu, 27 Sep 2018 14:53:42 GMT
Igniters,

Code Freeze date is tomorrow. Bad news is that we still have a number of
important features not-yet-merged (of most important - some MVCC stuff,
TDE, PHP/Python clients). Good news is that we made a good progress with
scope decrease. I propose the following release plan then:

1) By 30 Sept, only tickets critical for AI 2.7 release should have 2.7 fix
version. I expect that there should be about ~30 tickets, and most of them
are critical bugs (either existing or in new features). This is what we
call Code Freeze. From this time it is not allowed to add any tickets to
2.7 unless you are able to prove that it is a blocker for the release. This
means absolute ban for any new features.
2) Then we take *3 weeks for stabilization*: 1 Oct - 22 Oct. During this
time we fix all known bugs in new features, and finalize those new features
which are slightly behind a schedule. I would even suggest to take *4 weeks
for stabilization* (1 Oct - 29 Oct)
3) Once stabilization is over, we start vote.

This big stabilization window is essential for us, as current release will
contain a lot of huge features, which should be tested thoroughly before
going public. But the very critical ingredient here - *no new tickets on AI
2.7* during this phase except of critical bug fixes found during
stabilization phase.

In the end we will have nice and well tested AI 2.7 at the end of October.

What do you think about it?

Vladimir.


On Mon, Sep 24, 2018 at 3:11 PM Nikolay Izhikov <nizhikov@apache.org> wrote:

> Hello, Petr.
>
> My suggestion is to migrate to a newer version of GPG and throw an error
> message if one use old version.
>
> В Пн, 24/09/2018 в 14:53 +0300, Petr Ivanov пишет:
> > I’ve checked the changes and they are good both on old and latest
> versions of Ubuntu.
> >
> >
> > However, I’ve stumbled upon another problem — GPG: current release
> scripts do not honour latest GPG versions.
> > I can introduce corresponding changes, but question is — should release
> script check for GPG version and have 2 version of signing commands or just
> warn user about old version of GPG and exit?
> >
> >
> > > On 21 Sep 2018, at 19:46, Nikolay Izhikov <nizhikov@apache.org> wrote:
> > >
> > > Hello, Petr.
> > >
> > > Seems that rpm build script doesn't work on a lates Ubuntu Linux.
> > > I've created a ticket [1] and found a fix for it [2]
> > >
> > > With one line fix rpm build is working under my environment.
> > > Can you check fix on your environment?
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-9665
> > >
> > > [2] https://github.com/apache/ignite/pull/4808
> > >
> > > В Пт, 21/09/2018 в 16:22 +0300, Petr Ivanov пишет:
> > > > Hi, Nikolay
> > > >
> > > >
> > > > I’ve tested vote_3_step_1 and vote_3_step_2 scripts from [1] and
> they are OK.
> > > > My configuration:
> > > > - generated gnupg key (~/.gnupg)
> > > > - Ubuntu 16.04 (with latest updates)
> > > > - packages: subversion git unzip alien rpm fakeroot gcc dpkg-sig
> gnupg-agent
> > > >
> > > > Please double check you environment for release procedure
> > > >
> > > >
> > > > [1]
> https://ci.ignite.apache.org/viewLog.html?buildId=1914618&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote&tab=artifacts#!hkm8d5gqy4ii
> > > >
> > > >
> > > > > On 20 Sep 2018, at 17:39, Nikolay Izhikov <nizhikov@apache.org>
> wrote:
> > > > >
> > > > > Hello, Igniters.
> > > > >
> > > > > I've started to write Wiki article for a future Release Managers.
> > > > > Since release process doesn't described anywhere public I do it
> while releasing 2.7:
> > > > >
> > > > >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+manager+Notes
> > > > >
> > > > > Any feedback is strongly appreciated.
> > > > >
> > > > > I've tried to walk through vote steps in release procedure and
> found some issues:
> > > > >
> > > > > Some of them we already fixed with Petr Ivanod and Anton
> Vinogradov.
> > > > > Thank you, guys!
> > > > >
> > > > > For now, I stuck on the following issue:
> > > > >
> > > > > `vote_3_step_1\[packages\]build.sh` is broken.
> > > > > I got following output:
> > > > >
> > > > > ```
> > > > > RPM build errors:
> > > > >   bogus date in %changelog: Fri Jun 17 2018 Peter Ivanov <
> mr.weider@gmail.com> - 2.6.0-1
> > > > >   File not found:
> /tmp/tmp.EezfJVTwLm/BUILDROOT/apache-ignite-2.6.0-1.x86_64/usr/share/doc/apache-ignite-2.6.0/MIGRATION_GUIDE.txt
> > > > > + processTrap
> > > > > + echo 'Removing temporary work directories:  /tmp/tmp.EezfJVTwLm'
> > > > > Removing temporary work directories:  /tmp/tmp.EezfJVTwLm
> > > > > + rm -rf /tmp/tmp.EezfJVTwLm
> > > > > ```
> > > > >
> > > > > 1. Script uses version number 2.6 somehow.
> > > > > 2. It fails because MIGRATION_GUIDE file doesn't exists.
> > > > >
> > > > > Is there anybody who can help with this issue?
> > > > >
> > > > >
> > > > >
> >
> >

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message