Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [escet-dev] Eclipse ESCET first release
  • From: Dennis Hendriks <dh_tue@xxxxxxxxxxx>
  • Date: Thu, 22 Oct 2020 07:34:11 +0000
  • Accept-language: nl-NL, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1XmbEcspikItN4q5qXDxvcLiXXRFSCXGpSvj8Tn1I9Y=; b=ig/9cp09mtdlPd+I2UAq3+ILc3wSyUSI9phD0DuYqEvx7mjaV5M4kCxyEnbG2z4GiKXP+bIlsUkezrk3sM5BZUek4+K51pLnKXBmaUYONhT3+pXqqqegIMH6BVjvzZqpF6neHL+zkNGOGgTp9BDIRoTVSyS79shEiFrZEGm25MChU86qHC4OtxnGds/ZkaHc6+sbF+K1+lWWVNQC+tBg51EyajDiggq22DW/KknvhQLg7NMgfPmXqP2/Zhs025Ja0K/1fUkJMwHgHRUAe/ClSaUGN68yEdZ/62Ila/lH7MITeo1n1GA1RaZblWQeHJ/HSq/oM2qSLtySzmhoKpznNQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=NHD5FNr13983xVPG5DM8XQKgumNv5lYl003Xb6J+jjzw2yMtww92mnESF40PvYrIyyPofGCi/jLnkHTKddk65tpycq3VENojis4bKaB6oroOLdH2Wu+5mfNN3iPTTCdprMltzTMtHE7PYZLtwRcUNTRFYLjiPJoB4p+Pir8lciCw7sb+mcIU3Pbs+DvJmDkDXDJi+PKPb1MR4kgFXpEo7vvJOw/imxGtHSnDtMfhFtyaqqPrLwV3mZNBf/uCm904VMp89zxRlXjzc2+W06jNc5vgj8I4c72ul3J2mqqInyEg8fb1kvosJ2vX+eWpIoI0HilQy+gZMxqLBrjV7YBBTg==
  • Delivered-to: escet-dev@xxxxxxxxxxx
  • List-archive: <https://dev.eclipse.org/mailman/private/escet-dev>
  • List-help: <mailto:escet-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://dev.eclipse.org/mailman/listinfo/escet-dev>, <mailto:escet-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://dev.eclipse.org/mailman/options/escet-dev>, <mailto:escet-dev-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHWo8M1o5n2x8TLXUSE8+Lhs6A3DKmedb7rgAAvaM+ABJ6ROg==
  • Thread-topic: Eclipse ESCET first release
I think we can finalize the plan. I'll file an official release plan and create the issues for release 0.1 in GitLab.

Dennis

Van: Dennis Hendriks <dh_tue@xxxxxxxxxxx>
Verzonden: maandag 19 oktober 2020 11:07
Aan: escet developer discussions <escet-dev@xxxxxxxxxxx>
Onderwerp: Re: Eclipse ESCET first release
 
Hi Albert,

> Looks good to me, for as far as I understand it.

Is there anything in particular not clear to you? Anything you want me to explain in more detail?

> A bit more down to earth, should we discuss gitlab configuration?

May be good idea indeed. Maybe create a separate dev-list discussion for this, to keep this current discussion focussed on the scope and planning of the first release?

> Codestyle conventions is another topic.

That would ideally be yet another separate discussion I think, to keep discussions focused.

Kind regards,
Dennis Hendriks
Eclipse ESCET project lead

Van: escet-dev-bounces@xxxxxxxxxxx <escet-dev-bounces@xxxxxxxxxxx> namens Hofkamp, A.T. <A.T.Hofkamp@xxxxxx>
Verzonden: maandag 19 oktober 2020 08:25
Aan: escet developer discussions <escet-dev@xxxxxxxxxxx>
Onderwerp: Re: [escet-dev] Eclipse ESCET first release
 
Hello,

Looks good to me, for as far as I understand it.

A bit more down to earth, should we discuss gitlab configuration?
Issue tags and milestones at least I think, and probably branch usage/names/conventions?
Codestyle conventions is another topic.

In general, I think less is more here.

Albert

From: escet-dev-bounces@xxxxxxxxxxx <escet-dev-bounces@xxxxxxxxxxx> on behalf of Dennis Hendriks <dh_tue@xxxxxxxxxxx>
Sent: Friday, October 16, 2020 16:06
To: escet-dev@xxxxxxxxxxx <escet-dev@xxxxxxxxxxx>
Subject: [escet-dev] Eclipse ESCET first release
 
Hi all,

Now that our initial contribution has been given 'check-in' approval, it is time to start planning our first release.

This will be our first release. The release version will be '0.1'. All plug-ins etc in the initial contribution already have this version number.

I propose that for the first release, we focus only on getting to that first release based on the initial contribution, rather than adding new features, etc. This ensures we can get a first release as quickly as possible, such that everyone can use it.

I think the following is needed to get to a first release (not necessarily in this order):
  • Create a release plan (this post is to start the discussion on that).
  • Commit the initial contribution.
  • Get final approval for the initial contribution.
  • Wait for a Jenkins instance (JIPP, Jenkins Instances Per Project) to build the release. I've already requested it. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=567931.
  • Await approval for the third party dependencies and contribute them to Eclipse Orbit.
  • Get the build working on our JIPP.
  • Add JAR signing.
  • Configure for deployment to Eclipse Foundation infrastructure.
  • Think about and build nightly/weekly integration builds, milestones and release candidates.
  • Adhere to all required release, branding and IP requirements.
  • Ensure project metadata is up-to-date.
  • Ensure our IP log is up-to-date.
  • Perform a release review.
  • Perform the release.
Given that this is our first release, there are items on this list that are new to us. Also, approval is required for several of the items. As such, this may take a while. I propose to pick a date we are fairly certain we can meet. Then we may still surprise ourselves and release earlier if possible.

I propose to set the preliminary release date on March 31, 2021.

Let me know what you think about this proposal.

Kind regards,
Dennis Hendriks
Eclipse ESCET project lead

Back to the top