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 Tue, Jun 11, 2013 at 11:13 PM, Ed Willink <ed@xxxxxxxxxxxxx> wrote:

I think a certain amount of self-policing is possible for the many 'minor' projects. Their consumers are surely well aware how stable builds are and how much credible development is going on. Concerned projects should perhaps contact the EMO at M6 to complain about the lack of M4 project plan and request a firm commitment to either a frozen/point/minor/major release.

For 'major' projects I'm not sure what can be done. Surely EGIT has enough experienced committers to know that a major new release at SR2 RC3 is not the way maintenance is done? Perhaps the EMO should enforce only PMC-approved major or point version changes after M6, and AB-approved after M7. NB thais includes SR1 and SR2 that should be maintence. If there is a new release it is new not maintenance.

I am not aware of any EGit major release we would have done for a SR2. We release roughly every 3 months
and we don't have the bandwidth to maintain several versions in parallel. So far we did major versions with SR0
and delivered minor version releases with SR1, SR2 and an additional one in Dec.


Back to the top