Hi Brett,
Probably the only hesitation would be if it absorbs time that prevents
> getting the release out, since it sounds important - but if you can manage,
> go for it.
Your hesitation may be justified. Considering the security update it
probably makes sense to cut a quick release and plan a
Hi Brent,
Migrating to git and getting a timely release out to make sure everything works
sounds good. Probably the only hesitation would be if it absorbs time that
prevents getting the release out, since it sounds important - but if you can
manage, go for it.
Let me know how I can help... I d
Louis,
It seems like I may have been unclear. I'm actually proposing a migration
of the Apache Continuum project itself, not new functionality. The only
thing the 1.4.3 release would include is security updates and fixes. I'm
just looking to use it as an opportunity to change and document the rele
I would love to see GIT support - it would be a great addition for a
migratory path - legacy on SVN, new projects on GIT/GitLab/GitHub/ - and
with the new processes and tools available for release handling - it could
provide a lot of value to the user community.
Continuum is still a great and easy
Greetings,
I would like to re-open this discussion in the context of a 1.4.3 bugfix
release.
The git mirror grants many of the same benefits of git, but having both
subversion and git involved in the development and release processes adds
complexity. I would like to simplify and gain the ability
