Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What is the branching strategy used in JabRefs SVN repository?

April 26, 2017branching JabRef Repository strategy SVN Used

0

10 Posted

What is the branching strategy used in JabRefs SVN repository?

1 Answer

0

Posted

The trunk is used for developments targeted for the next release. When we release the first beta of a new version, e.g. 2.4, we make a branch (beta_2.4). From that moment, all changes that are to be part of the 2.4 version must be made in the branch, while changes that are for the following version must be made in the trunk. This lets us polish the 2.4 version while at the same time checking in features for version 2.5. When 2.4 is finished, it is built from the beta_2.4 branch, and then all changes that have been made in the beta_2.4 branch since it was created are merged into the trunk. At this point the trunk has all the changes of the 2.4 version, in addition to whatever has been done in the trunk in the meantime.