This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 09 Nov 2015 17:27, Tristan Gingold wrote: > there was a lot of work on binutils recently (nice!). > Previously, I tried to find a period of calm to create > a release branch, but I wasnât able to this year. > > So, how to process ? Is it reasonable to ask developers to > be quiet ? From my experience, it doesnât work very well > because we all want to push our new features in the next > release, so instead of being quiet developers hurry up. > > I could also create a branch from a past point, but all > the bug fixes wonât be in the new release, so there would > be additional backport work. i think it's reasonable to have a feature freeze date, and then a branch date some weeks after that. glibc/gcc does a similar thing. with git, it's a lot easier to backport/cherry-pick changes too. -mike
Attachment:
signature.asc
Description: Digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |