ESP-IDF 1.0 Release plan

[Ritesh]

The repository has a main branch where all our current work will be done. This branch will always contain our latest work, regardles of which esp-idf version is current. The repo also has a bunch of tags indicating the released versions. You can use them by cloning the repository and then doing something like 'git checkout v1.0' to switch to the official release. Also check out https://github.com/espressif/esp-idf/releases/tag/v1.0 , I just edited in how to obtain 1.0 in the end of that document.

Ok, So, I will get current update status by using "git pull" and "git submodule update" commands on which I am working on ESP32-idf RTOS SDK since one month.

Let me correct if i am wrong.

I have also checked that there is last commit of last Friday and after that there is no any commit inside ESP32-idf RTOS SDK on Git. So, when we will get next update for remaining drivers and other stuffs which are remaining to include it.

[slcasner]

Please update the http://www.espressif.com/en/products/ha ... /resources page to show the current version 1.0 and release date for the ESP32 IDF RTOS SDK. I was watching there and did not notice that v1.0 was released on github.

[ESP_Sprite]

I think it actually was just updated. Sorry, the release itself is done by another sert of people than the website, so it may lag slightly. I think following Github would be a better option; that's where new releases are put by the devs so you should see it there immediately.

[Ritesh]

I think it actually was just updated. Sorry, the release itself is done by another sert of people than the website, so it may lag slightly. I think following Github would be a better option; that's where new releases are put by the devs so you should see it there immediately.

Ok, So, I will get current update status by using "git pull" and "git submodule update" commands on which I am working on ESP32-idf RTOS SDK since one month.

Let me correct if i am wrong.

I have also checked that there is last commit of last Friday and after that there is no any commit inside ESP32-idf RTOS SDK on Git. So, when we will get next update for remaining drivers and other stuffs which are remaining to include it.

[rudi ;-)]

...commands on which I am working on ESP32-idf RTOS SDK since one month.

Let me correct if i am wrong.

I have also checked that there is last commit of last Friday and after that there is no any commit inside ESP32-idf RTOS SDK on Git. So, when we will get next update for remaining drivers and other stuffs which are remaining to include it.

Start my personal opinion


Ritesh:

This must be times, sorry:

And if you ask 1000 times the same ask, please, just follow the thread, if there is something new there will be posted.
If it lags many times, it would be better, you pursue the source directly in github.

Every change and new is logged via the github.
So if you have a github account you can subscribe to the channel of esp-idf. Automatically every step, every problem, every merging is communicated to you. Sometimes even more than it is announced here or it is communicated.
And you can make code proposal and can request a Pull ( merge your code to the MASTER ) .. and so on.

Also you can communicate immediately over the channel and problems directly over github, this is nevertheless a news message thread.

I do not understand your constant post around the same questions in the NEWS honest.

When NEWS is finished it will be ready and will be communicated.
This important NEWS thread constantly with the same garbage to attack does not make it clearer!

You're not a beginner anymore?
You know how github works?
If not, in many ways it is better to start first with github how it works?
this makes life easy.

Because the notification of github about new patches, new tags new releases and so on works great.
you see each detail on it, where, when, who is working on drivers, news, patches, from where it comes and so on.

Branches: Master ( usually allways up2date - )
other branche, if you want try other things: bugfix/uart_isr_rodata
but this : This branch is 270 commits behind master.
so "OLD"

somtimes branches can be experimental for testings
if the code then is stable, then it will be merged into MASTER..
and perhabs in a release, example by tags:

tags: v0.9, ( release 0.9 ) , v1.0 ( release 1.0 )
and this can be same, older as the Master.
you must start with github first Ritesh.
then many question in this NEWS Thread will be answered auto for you.




This then better to create a new Thread "How Github works" in general discussion ,
but not "annoy" in NEWS Channel Top Theme

Because all here are constantly notified via email with new NEWS contributions, if this thread is updated.
Because i write here , each User will update with notification over email too.. ( sry guys for this onetime )

One logs in and then expects a news post from the developer team.
Instead, you read then beginner questions to Gitub and always the same questions from you.
(Proposal: google: how github works).

End my personal opinion

[Ritesh]

...commands on which I am working on ESP32-idf RTOS SDK since one month.

Let me correct if i am wrong.

I have also checked that there is last commit of last Friday and after that there is no any commit inside ESP32-idf RTOS SDK on Git. So, when we will get next update for remaining drivers and other stuffs which are remaining to include it.

Start my personal opinion


Ritesh:

This must be times, sorry:

And if you ask 1000 times the same ask, please, just follow the thread, if there is something new there will be posted.
If it lags many times, it would be better, you pursue the source directly in github.

Every change and new is logged via the github.
So if you have a github account you can subscribe to the channel of esp-idf. Automatically every step, every problem, every merging is communicated to you. Sometimes even more than it is announced here or it is communicated.
And you can make code proposal and can request a Pull ( merge your code to the MASTER ) .. and so on.

Also you can communicate immediately over the channel and problems directly over github, this is nevertheless a news message thread.

I do not understand your constant post around the same questions in the NEWS honest.

When NEWS is finished it will be ready and will be communicated.
This important NEWS thread constantly with the same garbage to attack does not make it clearer!

You're not a beginner anymore?
You know how github works?
If not, in many ways it is better to start first with github how it works?
this makes life easy.

Because the notification of github about new patches, new tags new releases and so on works great.
you see each detail on it, where, when, who is working on drivers, news, patches, from where it comes and so on.

Branches: Master ( usually allways up2date - )
other branche, if you want try other things: bugfix/uart_isr_rodata
but this : This branch is 270 commits behind master.
so "OLD"

somtimes branches can be experimental for testings
if the code then is stable, then it will be merged into MASTER..
and perhabs in a release, example by tags:

tags: v0.9, ( release 0.9 ) , v1.0 ( release 1.0 )
and this can be same, older as the Master.
you must start with github first Ritesh.
then many question in this NEWS Thread will be answered auto for you.




This then better to create a new Thread "How Github works" in general discussion ,
but not "annoy" in NEWS Channel Top Theme

Because all here are constantly notified via email with new NEWS contributions, if this thread is updated.
Because i write here , each User will update with notification over email too.. ( sry guys for this onetime )

One logs in and then expects a news post from the developer team.
Instead, you read then beginner questions to Gitub and always the same questions from you.
(Proposal: google: how github works).

End my personal opinion

Hi,

I know how GIT commands are working and how GIT Repository is working. I have just asked questions as i don't see any update since last Friday on github. My concern was that we are waiting for I2C Drivers and other stuffs which are urgent for us.

That is why i am asking that type of question frequently to get any update for that.

Sorry if I have asked any questions multiple times or forcing for anything.

[rudi ;-)]

Sorry if I have asked any questions multiple times or forcing for anything.

Thanks for your understand.

[jumjum123]

@Ritesh, did you take a look to arduino components ?

[rudi ;-)]

@Ritesh, did you take a look to arduino components ?

No i think he did not.
He do start PM me now.

..So, Please let me know if you have idea means by the end of this week or by the end of next week to get I2C driver included into ESP32-idf RTOS SDK...

@Ritesh
yes and no:
if i know, then yes,
no not only you, i will post to community

have a look to this post:

http://esp32.com/viewtopic.php?f=19&t=632#p2738

best wishes
rudi

[Ritesh]

@Ritesh, did you take a look to arduino components ?

Yes, I have looked Arduino code initially when UART driver was not released by Espressif System. But what actually happened is that we have taken that Arduino Driver and spared sometimes to port and it worked ta that time. After that again we need to report actual UART driver which was released by Espressif System.

So, Again we need to spare sometime again to port it and need to debug if anything not working.

So, I prefer to wait till release by Espressif System otherwise we need to put two times effort for such stuff which are not released yet..

I hope you understand my concern or point.

Let me know if you have any questions for that.