Re: [jgit-dev] [cross-project-issues-dev] Question on Kepler SR1 release

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [jgit-dev] [cross-project-issues-dev] Question on Kepler SR1 release review

From: Matthias Sohn <matthias.sohn@xxxxxxxxx>
Date: Wed, 14 Aug 2013 20:48:33 +0200
Delivered-to: jgit-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/jgit-dev>
List-help: <mailto:jgit-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/jgit-dev>, <mailto:jgit-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/jgit-dev>, <mailto:jgit-dev-request@eclipse.org?subject=unsubscribe>

On Wed, Aug 14, 2013 at 5:39 PM, David M Williams <david_williams@xxxxxxxxxx> wrote:

Its "new" as of last April.

was this decision mentioned on this list ? I wasn't aware of it and also can't find

an announcement in the cross list's archive.

This means we'll ship EGit 3.1 not with Kepler SR1 but from our own updates site

since 1 month before SR1 already passed.

And, by all means ... fix bugs and then submit a maintenance release for final version (which would not need a "new release").

"Released", in this context, means the formal Eclipse process of having been through the required release review which is always required of new releases.

Matthias

Prev by Date: [jgit-dev] Pull Accepting Remote's Changes in a Conflict
Next by Date: [jgit-dev] Fwd: [technology-pmc] FYI: Policy on new releases joining SR
Previous by thread: [jgit-dev] Pull Accepting Remote's Changes in a Conflict
Next by thread: [jgit-dev] Fwd: [technology-pmc] FYI: Policy on new releases joining SR
Index(es):
- Date
- Thread

Breadcrumbs