Re: [epsilon-dev] Epsilon 1.5 Release

[Dimitris Kolovos <dimitris.kolovos@xxxxxxxxxx>]

Hi Sina,

My rationale for proposing this is that we don't have ways of making
the new (parallel, incremental) module implementations available to
end users through the development tools (launch configuration UIs, ANT
attributes/nested elements). This means that very few end users would
benefit from these at this stage while there's some risk that some of
the changes in the underlying EOL/EMF-EMC classes could introduce
regressions that are not caught by our unit tests.

As such, I would be inclined to

- Release 1.5 as-is
- Add the required extension points/UIs/ANT attributes for new module
implementations
- Merge the parallel and incremental work in the main repo

Any thoughts on this would be more than welcome.

Cheers,
Dimitris

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,
>
>
>
>
>
> [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