Github - bitcoin commit break?

[Diapolo]

Perhaps that's the wrong place to ask, but I would like to now how long there will be a commit break. I added a few commits, which come from one local source and it get's hard to keep track of the different commits . Is the normal process to switch to 0.7 now on Git?

Dia

[1714142109]

1714142109

[1714142109]

1714142109

[1714142109]

1714142109

[Red Emerald]

commit break?

[Diapolo]

commit break?

Perhaps it WAS the wrong place ^^ ... there were now new commits / updates included in the source over at Github for 3 days, since the 0.6 final release was made.

Dia

[binpool.de]

wtf is a commit break?

[Diapolo]

Please ask google or whatever search engine you like, what a commit on Github is. And by break I meant simple some kind of pause and no error or a defect!

*/me knew this was a bad idea to post this in here ^^*

Dia

[Pieter Wuille]

We were still deciding on what the next version would be, and what its goals would be.

Next version will probably be 0.6.1, and include mainly cleanups, bug fixes and other small improvements.

[Red Emerald]

Please ask google or whatever search engine you like, what a commit on Github is. And by break I meant simple some kind of pause and no error or a defect!

*/me knew this was a bad idea to post this in here ^^*

Dia

Why would there ever be a pause in development?

[m3ta]

Please ask google or whatever search engine you like, what a commit on Github is. And by break I meant simple some kind of pause and no error or a defect!

*/me knew this was a bad idea to post this in here ^^*

Dia

Why would there ever be a pause in development?

"commit freeze" is the correct term.

During software development there are often time when working software release must be prepared for customer evaluation of internal testing. Many software release managers use a feature called “commit freeze“: no one can commit to main branch of development (trunk/master) until release is packaged. 

Also, Google is your friend. Well, it's my friend, it seems it isn't /yours/.

[realnowhereman]

Just because the main branch goes into feature freeze doesn't mean work on the development branches has to halt; and I'm sure the developers all carry on working on their own working copy even if github goes quiet for a while.  Isn't that the whole point of git?

[Diapolo]

Just because the main branch goes into feature freeze doesn't mean work on the development branches has to halt; and I'm sure the developers all carry on working on their own working copy even if github goes quiet for a while.  Isn't that the whole point of git?

The initial question was not about the developers doing a break, but about don't accepting / merging commits into the main branch .

Dia

[Pieter Wuille]

The development process consists of this cycle (in a perfect world, at least):

• the "merge window" for a new version opens
• complete and accepted pull requests are merged into the master branch
• the "merge window" closes (it usually remains open for a few weeks)
• a release candidate is built
• the release candidate is tested
• if found necessary, fixes (but no new features) are merged, and a new release candidate is built.
• if the last release candidate survives testing, it is renames and released as final
• repeat