Hi Ming, All. The release date is set in JIRA.
For your convenience, here are the release notes: Release Notes <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318620&version=12338559> Please let me know when the website is fixed. Best regards, Pierre Smits V.P. Apache Trafodion On Mon, Mar 12, 2018 at 1:16 AM, Liu, Ming (Ming) <[email protected]> wrote: > Hi, Pierre, > > The release date is March 10. The only left step is update the web site, > then I will announce the release. > Please help to set the JIRA pull-down list , thanks. > > Ming > > -----Original Message----- > From: Pierre Smits <[email protected]> > Sent: Sunday, March 11, 2018 11:24 PM > To: [email protected] > Subject: Re: The importance of 'fix version' in the JIRA, please fill it > correctly > > HI Ming, > > What is the release date we're going to use for the 2.2 release? I can > having it set in JIRA so that 2.2 doesn't pop up anymore in the pull-down > for the fix versions. > > Best regards, > > Pierre Smits > > V.P. Apache Trafodion > > On Sat, Mar 10, 2018 at 11:23 AM, Ming Liu <[email protected]> wrote: > > > Hi, all, > > > > When I prepare the Release Note for R2.2.0, I found a problem that > > developers sometimes wrongly specify the 'fixed version' as R2.2, but the > > real fix code not merged into R2.2 branch. > > > > Now R2.2 is closed for code merge, so any new JIRA or ongoing JIRA, > please > > DON"T use R2.2 as the 'fix version'. > > > > The best practice is not fill in 'fix version' until one resolve the > JIRA, > > so he/she knows which branch the code merged into. > > > > The current main branch is for R2.3. When R2.3 branch is created, any new > > JIRA closed should also notice if you check in the fix into R2.3 branch > or > > main branch and fill in the 'fix version' correctly. Since we use JIRA's > > filter to generate the release note, so please all contributors help to > > notice this ^_^ > > > > Thanks all, > > Ming > > > > >
