Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Missing release information for some Kepler projects

On Wed, Jun 12, 2013 at 12:47 AM, Ralf Sternberg <rsternberg@xxxxxxxxxxxxxxxxx> wrote:
I don't know about the SRs but I remember that EGit updated from 1.3
to 2.0 in Juno RC2 or RC3. For me this feels like a pretty risky
change for an RC. I don't mean to point the finger at EGit, I just
think we should agree that RC1 should really be a "release candidate",
i.e. almost the thing that is going to be released except for some
minor fixes. The code should cool down after that point. At least
major versions should not change anymore.

I agree we should contribute to the release train earlier than that.
Due to our faster release cycle (4 releases per year) M6 is
usually shortly after our previous release in the same year.
Hence for Kepler we did the first 3.0 contribution with M7.

AFAIK those who depend on us know our nightly build, watch code
reviews and discussions on our mailing lists and speak up early in
case they see a problem. 


Back to the top