Hi Alan,
Releasing regularly new versions of the package is always good: it instills
confidence in users that they are using a software package that is being
actively developed and maintained.
However, I do think that the approach of having bug-fix branches is essential
when making regular
Hi Tom:
On 2016-09-22 13:54+0100 Tom Schoonjans wrote:
> In the scenario I am suggesting, you would just end up with a new
branch that starts at a tag and will contain bug fixes only. It will
never need to be merged into master as it will consist of commits that
were cherrypicked from master.
>
Hi Tom:
At the end of this I have a question concerning using our preferred
workflow at github (assuming someone wants to take responsibility for
such a move).
But first, you need some background. PLplot used CVS for a long time,
then SVN for a long time, and then fairly recently made the
Hi Tom:
You have opened up a lot of interesting topics for discussion here
which I am going to answer in separate e-mails with separate subject
lines.
In those separate replys I will also quote some key questions that
Hazen has already asked.
More later...
Alan
__
Alan
Hello again,
> We have been trying to maintain a linear history with git following the
> process explained in the README.developers file. I think that the fork and
> pull-request system would break this?
Not necessarily, you can ask people submitting a PR that they rebase against
master. You
On 2016-09-21 14:22+0100 Tom Schoonjans wrote:
> Hi all,
>
>
> I was wondering if a new release of PLplot could be made soon, as the current
> release does not build with CMake 3.6.x? The fix for it is currently in
> master.
>
> Many thanks in advance and best regards,
Sorry, but we are not
