Re: [che-dev] Dev process

[Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx>]

Hello Devs

In general we are done with moving 4.0 in master.

From now on 3.x version moved from master to 3.x branch

We may have some unstable period I hope until tomorrow all will be fine.

If someone has some major issues please let me know.

Also due to the change this PR was automatically closed

https://github.com/codenvy/che-core/pull/530

https://github.com/codenvy/cloud-ide/pull/198

https://github.com/codenvy/che-depmgt/pull/55

https://github.com/codenvy/che-plugins/pull/463

https://github.com/codenvy/che-plugins/pull/478

https://github.com/codenvy/che-core/pull/532

https://github.com/codenvy/che/pull/117

https://github.com/codenvy/che-core/pull/501

https://github.com/codenvy/che-core/pull/507

https://github.com/codenvy/che-core/pull/509

https://github.com/codenvy/che-core/pull/517

https://github.com/codenvy/che-core/pull/513

https://github.com/codenvy/che-core/pull/458

https://github.com/codenvy/che-core/pull/477

https://github.com/codenvy/che-core/pull/514

https://github.com/codenvy/che-core/pull/521

https://github.com/codenvy/che/pull/118

https://github.com/codenvy/che-plugins/pull/474

https://github.com/codenvy/che-plugins/pull/465

https://github.com/codenvy/che-plugins/pull/467

https://github.com/codenvy/factory/pull/42

If you are an author and feel that it's still have some value. Please create new PR to the correct branch. 

Sergii Kabashniuk

On Thu, Dec 17, 2015 at 3:26 PM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

We are going to start branches switch.

On Wed, Dec 16, 2015 at 3:21 PM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

Hello

In Thursday 17 of December at 15.00 Kiev, 13.00 UTC  time we are going to start changing branches position

4.0->master

master->3.x

After the end of this procedure we recommend you to download git repositories from the scratch

On Thu, Dec 10, 2015 at 4:10 PM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

Hello

Guys we are not able to switch branches this week.

Will do it next week.

Exact time when I'll going to announce before we actually do that.

Sorry for inconvenience

On Wed, Dec 9, 2015 at 5:46 PM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

https://github.com/codenvy/che-core/pull/454

https://github.com/codenvy/che-core/pull/455

https://github.com/codenvy/che-core/pull/456

https://github.com/codenvy/che-core/pull/459

https://github.com/codenvy/che-core/pull/478

https://github.com/codenvy/che-core/pull/485

https://github.com/codenvy/che-core/pull/491

This one now in the state of checking and I hope we will merge it before the switch.

On Wed, Dec 9, 2015 at 5:42 PM, Sharafy, Tareq <tareq.sharafy@xxxxxxx> wrote:

Hi Sergii,

There are several pull requests pending on the current master branch. Will they be merged before the switch? If not, where will they be merged after the switch?

thank you
Tareq Sharafy

From: che-dev-bounces@xxxxxxxxxxx [mailto:che-dev-bounces@xxxxxxxxxxx] On Behalf Of Sergii Kabashniuk
Sent: Wednesday 09 December 2015 17:26
To: che developer discussions <che-dev@xxxxxxxxxxx>
Subject: Re: [che-dev] Dev process

 

Hello

In Thursday 9 of December at 15.00 Kiev, 13.00 UTC  time we are going to start changing branches position

4.0->master

master->3.x

After the end of this procedure we recommend you to download git repositories from the scratch

 

On Sat, Dec 5, 2015 at 7:50 PM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

Small updates

 

Next week we are going to switch our master branch.

will be:

master-->3.14.x

4.0 --> master.

 

Please make sure you are going to checkout, merge, rebase or create PR to the correct branch.

 

Exact time when I'll going to annonce before we actually do that.

 

Sergii Kabashniuk

 

 

On Thu, Sep 3, 2015 at 3:37 PM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

Hello developers.

 

Small updates.

 

1. We removed from our dependecy pom all unnecessary dependencies not related to che.

   For this moment this is only properties. But soon it will be actual dependency management.

   From this time if you want to introduce new dependency or change dependency version  it have to be approved by Eclipse

   List of already approved dependencies is here 

   https://dev.eclipse.org/ipzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&component=technology.che&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=

   See state approved.

 

2. I've put here 

   https://github.com/codenvy/codenvy-dev-resources/blob/master/che-codestyle/src/main/resources/che-codestyle-intellij.xml

   Intellij source code formatter that all developers should use.

   In a couple of days in this mail list   we will initiate discussing about:

   Github pull request

   Code format 

   Findbugs issues. etc.

 

Feel free to add anything you need.

  

   

 

On Tue, Aug 11, 2015 at 5:29 PM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

Small updates

 

From 3.12 developers are able to use all Java 8 features. Java 8 become standard.

To declare you project is findbugs-free you can set up maven property <findbugs.failonerror>true</findbugs.failonerror>. Next time when some one add new bug  findbugs will fail maven build for you.

 

 

On Thu, Aug 6, 2015 at 12:28 PM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

 

 

On Thu, Aug 6, 2015 at 12:12 PM, Florent Benoit <fbenoit@xxxxxxxxxxx> wrote:

  Sergii,

 

is it possible to turn it into 'fail' mode (by overriding default findbugs configuration) for some maven modules/projects if there is no warning ?

So we're sure we're not introducing new failures (as it won't build the module)

I suppose yes.

I'm open for PR 

 

Regards,

 

Florent

 

 

 

On Thu, Aug 6, 2015 at 10:58 AM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

Small updates

 

Findbugs enabled in warn mode. It means it won't fail if he found something suspicious

 

Please consider as best practices to fix issue reported by this tool.

If you have any suggestion about configuration of this tool please use che-dev mail list or ping me to discuss it.

 

Sergii Kabashniuk

 

 

On Tue, Jul 28, 2015 at 11:26 AM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

Small updates.

 

From 3.11.5 we enable by default "Error Prone" static code analysis (works during maven compile phase).

Please consider as best practices to fix issue reported by this tool.

If you have any suggestion about configuration of this tool please use che-dev mail list to discuss it.

 

FYI Findbugs is on the way.

 

Sergii Kabashniuk

 

On Tue, Jul 21, 2015 at 9:39 AM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

Small updates in our dependencies.

 

Servlet api 3.1.0

Jna 4.1.0

Git 2.4.5

 

 

About Java 8.

We found solution for problem with Java 8.

We expect to enable java 8 specific features in master after 3.11 release goes to production.

 

On Fri, Jul 3, 2015 at 11:07 AM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

Small updates

3.11 in master but we are going to postpone Java 8 features because we have same blockers with one of our plugins.

We are looking for solution. We let you know when we will found it. Meanwhile no Java 8 features allowed in master.

 

 

 

On Wed, Jun 3, 2015 at 11:34 AM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

Small updates.

1. Java 8 is set in master as build and runtime environment. Note no Java 8 specific feature allowed for this (3.10.x) version.

2. For 3.11 We may think about updates of guice to 4.0 and lucene for 5.1

 

On Tue, Jun 2, 2015 at 2:23 PM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

Small updates

We found that 4.0.0 works fine with Java 8 and we also want to speed up a bit java 8 integration so we decided to:

1. For 3.10 starting from June 3 enable Java 8 as target runtime and build environment. Source code allowed only Java 7 compatible. 

2. If everything is ok for 3.11 we will enable Java 8 features. Note that our GWT version is not allowed Java 8 specific features.

 

 

On Mon, May 25, 2015 at 4:52 PM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

Small updates

 

Our dev successfully set Java 8 as runtime environment for 4.0.0 for couple of days already. Everything looks normal.

With cautious optimism we can say that for  3.11 we can move to Java 8 too.

 

On Mon, May 11, 2015 at 12:05 PM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

Hello.

 

Some small news in our dev process.

1. With our new faster release schema we would like to introduce new annotation on our public REST API and SPI. 

   http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/annotations/Beta.html It has the same meaning as it have in guava

2. We would like to declare that we want to use Java 8 in our development (at least for 4.x) because EOL of Java 7. Our road map is following.

    1. We set Java 8 required to build 4.0. With compile source and target for Java 7

    2. In several weeks we will set up Java 8 as runtime enviroment for 4.0.0

    3. If we  do not receive any blockers from our testing enviroment for 4.0.0 we start thinking about moving to Java 8 for 3.x.

       It shouldn't happen closer then 1-1,5 from step 2.

 

 

Sergii Kabashniuk

 

 

 

 

 

 

 

 

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

 

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

 

 

 

 

 

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