Some additional rationale:
The original reason some people wanted a stable trunk branch was they
were concerned about the pace of development moving too fast, clearly
that's no longer a problem, now the stable development branch has become
an impediment as people on github can't see the development we are doing.
Even Apache board members looked at github and thought we had no commits
for 3 years.
We need people to see the ongoing work on River, so they have confidence
in the project's future and it's continued development and support.
Cheers,
Peter.
On 10/10/2020 9:03 AM, Peter Firmstone wrote:
Currently the trunk branch is a stable branch, it is not for
development code, let's make it so we can develop in trunk. The vote
concludes in two weeks.
+1 Peter.
Rationale:
The project needs to migrate from SVN to GIT.
The trunk branch is the GIT branch, currently it's only read only but
we can make it a live writable git repository simply with an INFRA
JIRA ticket.
https://github.com/apache/river
If we allow the trunk branch to become a development branch, then we
can move the current modular develpment branch into trunk, and migrate
other components not currently in the trunk branch like the ldj-tests,
surrogate and other bits and pieces, which are also in a development
state not ready for release. Note that these should probably go under
their own directory in trunk.
Doing this will preserve the commit history of Apache River.
Are there any git experts on the list?
If this is not the right way to go about the migration to git, please
give us your thoughts?
Regards,
Peter.
