Mail Archives: geda-user/2016/12/21/14:54:21
Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> Hi pcb Devs-
>
> It really is time to do a release of pcb. There have been a lot of bug
> fixes incorporated since the last release, and the distribution
> packages don't keep up with the latest git version.
>
> I wanted to start this thread to collect ideas and generally figure
> out how to execute this process, and hopefully push it forward. Being
> a relatively new developer to the project, I'm not entirely sure
> what's involved. So, let's start with some questions:
>
> Is there already a process in place for executing a release of pcb (or
> other gEDA tools)?
>
> I found this on the wiki:
> http://wiki.geda-project.org/geda:release_engineering . Is it still
> relevant?
>
> Should we consider first putting out a release candidate?
>
> Regarding packaging, do we create packages for distributions, or do
> the distributions to that themselves?
>
> I'm willing to spend some time to make this happen, but I need some
> guidance.
>
> Thanks,
> --Chad
Hi Chad,
Just a short reply ... I will need to find some time on #geda to
interactively discuss ... so here goes:
Yeah, I'm in the same situation ... never done a pcb release.
So I'm in favor for a release candidate for a practice run and see if
any unnoticed bugs emerge ;-)
I had a test drive session planned between Xmas and Newyearsday and
thanks to my fellow colleages at the dayjob will have to reschedule
this, as they let down on some projects which in turn has led to a time
squeeze for me into January ...
Major issue to contemplate on is the version number ... are we going the
"2.0" route or still remain in the "1.99" series (and what letter comes
after "z" .. "aa" ?
I would go for "2.0.RC1" ... like to hear opinions ...
Another one .. if I do a release branch, can anybody push to it ? and be
able to do hot fixes and stuff.
Kind regards,
Bert Timmerman.
- Raw text -