[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [epsilon-dev] Epsilon 1.5 Release
|
Hi Horacio,
Thanks for kick-starting this. Before we can release 1.5 we'll also
need to go through a release review. The process for doing this is
described in [1] but I have to remember all the fine details every
time I do this. I'll take the lead on this (most likely around
mid-May) and create an article on the Epsilon website that records the
required steps.
On a minor issue, the "to" field of your email reads "Epislon Project
developer discussions <epsilon-dev@xxxxxxxxxxx>" (note the "Epislon"
typo). Is this a local typo in your contact list or in the mailing
lists database?
Cheers,
Dimitris
[1] https://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews
On 27 April 2018 at 13:45, arcanefoam@xxxxxxxxx <arcanefoam@xxxxxxxxx> wrote:
> 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,
>
>
> [1] https://github.com/c4urself/bump2version
> [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
--
Dimitris Kolovos
Professor of Software Engineering
Department of Computer Science
University of York
http://www.cs.york.ac.uk/~dkolovos
EMAIL DISCLAIMER http://www.york.ac.uk/docs/disclaimer/email.htm
