Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [epsilon-dev] Epsilon 1.5 Release
Hi Sina,

Sorry for the radio silence. I do not have any big contribution pending for 1.5 - mostly I have been sending small improvements here and there.

Regarding bumpversion - I am all for automation, but I am not sure if we can achieve 100% on that. The process we need is:

* Change all pom.xml files to 1.5.0.
* Make sure the commit with POM versions set to 1.5.0 is buildable.
* Tag that commit as "1.5".
* Let Jenkins create the final 1.5.0 update site and other things.
* Copy 1.5.0 final Eclipse-based deliverables from Jenkins to their places.
* Create Eclipse Oxygen + Epsilon 1.5.0 distributions, upload to website.
* From the 1.5 tagged commit, run "mvn org.eclipse.epsilon:eutils-maven-plugin:deploy -Ddeploy.url="" href="https://oss.sonatype.org/service/local/staging/deploy/maven2">https://oss.sonatype.org/service/local/staging/deploy/maven2" to deploy the Maven artifacts to Maven Central. I'll need to do this myself, as I believe you do not have a GPG key that is authorized to do so.
* Bump versions to 1.6.0.qualifier and 1.6.0-SNAPSHOT and push to Git.
* Update the website accordingly.

Can we do all that just with bumpversion?

BTW, I have no problem helping out with the Linux version. Horacio, do you want to do the Windows one? I definitely cannot do the Mac one (I do not have one).

Kind regards,
Antonio

On 28 April 2018 at 10:32, Sina Madani <sinadoom@xxxxxxxxxxxxxx> wrote:

Hi Horacio,

 

Thank you for the news update. I was wondering what is the reason parallel and incremental changes won’t be part of version 1.5? Aside from the “mvn clean install” issue with the test plugins at least the parallel changes are ready (all tests passing etc.)

 

Thanks,

Sina

 

From: arcanefoam@xxxxxxxxx
Sent: 27 April 2018 15:02
To: Epislon Project developer discussions
Subject: [epsilon-dev] Epsilon 1.5 Release

 

Hello all,

 

Good news!, Epsilon 1.5 has been scheduled for release for the end of May.

 

To do so, we need to complete a couple of tasks.

 

1. Determine what goes in.

    Current work on incremental and parallel execution will NOT go into version 1.5. 

    If you are working on a driver/language/enhancement and consider it to be in a usable state (all functionality implemented and tested), reply to this email with your interest in making it part of the release. We will decide on a per-contribution basis.

 

2. Prepare the code for release

    This is mostly automated and only requires a manual update on the versions in all MANIFEST and pom files. @Antonio: I know you usually do this; I've had success in using bumpversion[1] to automate this process, let me know if you want us to set this up (a bit of manual work initially, but then it will be automated).

 

3. Release

    This should be automated

 

4. Create Full Distributions

    We would appreciate some help creating the Full Distributions, i.e. the windows/macos/linux Epsilon-ready eclipses you can download from the site. Please let us know if you can give a hand.

 

 

Also remember that if you have developed a driver/tool that is currently in EpsilonLabs you should configure it to be part of the EpsilonLabs update-site[2].

 

Cheers,

 

 

[2] https://eclipse.org/epsilon/doc/articles/labsupdatesite/

 


_______________________________________________
epsilon-dev mailing list
epsilon-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/epsilon-dev



--
Antonio Garcia-Dominguez

Back to the top