The policy changes of Webnotes Team

Hello, Guys, all comunity!

I'm starting this thread after a long talk with Marta Ross, and a clarification with Syedm about how the periodicity of the changes of WebNotes developers in a unique branch are leaving the crazy developers to adjust the new features, and maintain new applications development.


Marta and I invested some time during the afternoon to solve the recurrence of an application that is not shown on the desktop.

The issue is that a few weeks ago I commented on a necessary change in some files to solve this problem. Only about one or two weeks later the master development team made a big change in how frappe creates and handles the desktop icons, resuming the old standard "using the title of the app" instead of the name as suggested.

So far, no problem, except for the fact that after upgrading the installation of frappe, the icons disappeared again.

As well as follow the threads of the forums, I also listen to and review every commit on Github, I remembered what had happened that I could solve the problem.

The difficulty shown above is just one of a few that we are facing. What do we treat objectively is the need to implement a policy of releasing updates, so we can meet and developers and end users.


What I see is that first we need different branchs for each type of user.
  1. Master Developers
  2. Apps Developers
  3. End User
Another issue is set to be given the flow of publications in each branch. For example, some issues affect all members from all walks such as permissions, harsh changes in the core, and translation.


But reports and usability issues are more tied to the end users.


We are trying to develop new resources and keep our forks the most updated, however, this has a very high cost related to time, either for lack of knowledge of the impact of each change, or why some changes are affecting me in a way that should not.

Today I can not filter the updates that are of interest to me.

Another question is on stage update!

We need placements as alpha, beta, and production.


I think other members here, can also report their difficulties, so we can help this team to grow more and better.


--


Best Regards.

Maxwell Morais
Python Developer powered by Webnotes framework <3
+55 11 954329659



Note:

 

If you are posting an issue,

  1. We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
  2. Paste your code at http://pastebin.com or http://gist.github.com and send only the URL via email
  3. For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.

     

    End of Note



    You received this message because you are subscribed to the Google Groups “ERPNext Developer Forum” group.

    To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-developer-forum+un…@googlegroups.com.

    To view this discussion on the web visit https://groups.google.com/d/msgid/erpnext-developer-forum/CABK1YkO2Yyr1G6mG6fGh3%2BYPfu_YPkCcpKNve_af59O_Z2YWXA%40mail.gmail.com.

    For more options, visit https://groups.google.com/d/optout.
Max,

Thanks for the note, replies inline:

On 08-Jul-2014, at 1:32 am, Maxwell Morais <ma...@gmail.com> wrote:

Hello, Guys, all comunity!

I’m starting this thread after a long talk with Marta Ross, and a clarification with Syedm about how the periodicity of the changes of WebNotes developers in a unique branch are leaving the crazy developers to adjust the new features, and maintain new applications development.


Marta and I invested some time during the afternoon to solve the recurrence of an application that is not shown on the desktop.

The issue is that a few weeks ago I commented on a necessary change in some files to solve this problem. Only about one or two weeks later the master development team made a big change in how frappe creates and handles the desktop icons, resuming the old standard "using the title of the app" instead of the name as suggested.

So far, no problem, except for the fact that after upgrading the installation of frappe, the icons disappeared again.

As well as follow the threads of the forums, I also listen to and review every commit on Github, I remembered what had happened that I could solve the problem.

Max - I was there when the missing module patch was overridden, Nabin or Anand told me that the new one is the correct one.

We know this is a problem, let us fix this on priority.

The difficulty shown above is just one of a few that we are facing. What do we treat objectively is the need to implement a policy of releasing updates, so we can meet and developers and end users.

Point noted, but we are also nearing the end of a very big release. Already the support has been reduced (a great number of issues were reported and fixed by the paid subscribers and I am sure they will help everyone).

What we will do is that we will start putting release tags, so that those remain stable.

What I see is that first we need different branchs for each type of user. 
  1. Master Developers 
  2. Apps Developers 
  3. End User
Another issue is set to be given the flow of publications in each branch. For example, some issues affect all members from all walks such as permissions, harsh changes in the core, and translation.


But reports and usability issues are more tied to the end users.


We are trying to develop new resources and keep our forks the most updated, however, this has a very high cost related to time, either for lack of knowledge of the impact of each change, or why some changes are affecting me in a way that should not. 

We had a very very long discussion on this and we have not yet come up with a good plan. The system during a big release (large number of hot fixes) and between releases (fewer fixes, more features) should be different. 

A good way to make sure conflicts don’t enter the system is to send pull-request in the main fork for changes you make in frappe or erpnext. This will make sure your updates will be stable and you will also be forced to make generic updates, which will help everyone too. Right now the contributions we are getting from the community is by reporting of issues, which is great, but if there are more bug fixes also coming in, then we would be more aware of what kind of features are being built by the community.

If there are teams that are heavily customizing, it would be better if they contribute their framework / product level patches. Or you maintain your own fork and don’t pull the latest features. I don’t think there is a way around it.

Also we would be happy to give our feedback on your development for free, if you publish your contributions (which is hardly ever the case). That is why we are an open source project. You can’t have it both ways!


Today I can not filter the updates that are of interest to me. 

Another question is on stage update! 

We need placements as alpha, beta, and production. 


I think other members here, can also report their difficulties, so we can help this team to grow more and better.


--


Best Regards.

Maxwell Morais
Python Developer powered by Webnotes framework <3
+55 11 954329659




Note:

 

If you are posting an issue,

  1. We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
  2. Paste your code at http://pastebin.com or http://gist.github.com and send only the URL via email
  3. For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.

     

    End of Note



    You received this message because you are subscribed to the Google Groups “ERPNext Developer Forum” group.

    To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-developer-forum+un…@googlegroups.com.

    To view this discussion on the web visit https://groups.google.com/d/msgid/erpnext-developer-forum/CABK1YkO2Yyr1G6mG6fGh3%2BYPfu_YPkCcpKNve_af59O_Z2YWXA%40mail.gmail.com.

    For more options, visit https://groups.google.com/d/optout.



Note:

 

If you are posting an issue,

  1. We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
  2. Paste your code at http://pastebin.com or http://gist.github.com and send only the URL via email
  3. For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.

     

    End of Note



    You received this message because you are subscribed to the Google Groups “ERPNext Developer Forum” group.

    To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-developer-forum+un…@googlegroups.com.

    To view this discussion on the web visit https://groups.google.com/d/msgid/erpnext-developer-forum/C6BFE67F-C2D4-44B6-9951-4E8175365FDB%40gmail.com.

    For more options, visit https://groups.google.com/d/optout.