On Fri, Mar 2, 2018 at 8:19 PM, vitalije <vitali...@gmail.com> wrote:
> What about fixing bugs? Should they also go to devel? Heh. I was just going to write about this. Reminds me of this joke: In theory, theory and practice are the same thing. In practice they're different. > I have committed recently a fix for the bug that nobody has reported yet, but which has caused me some data loss. Your bug fix was what got me thinking. Imo, you did the right thing. Iirc, I merged master into devel shortly thereafter. The problem with committing anywhere *except* master is that it doesn't fix master :-) There are two problems with committing only in master: 1. It doesn't follow the expected development pattern. 2. Devs won't routinely test the fix when they use anything in devel or based on devel. Imo, the solution is to commit urgent fixes to master *and* devel, by committing to master and then merging master into devel. Of course, all unit tests should pass in master before committing, but that's also true for committing to devel. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to firstname.lastname@example.org. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.