Let's not get bogged down on exact version numbers. They never meant anything to us except increasing all the time.
I heard a number of people complaining about "stuff that broke in a new release in Padre". It happened to me a number of times. We need to find a way to avoid that. This might be a good reason to move to github where merging and merge management is easier. We might also need to change our development model to a more controlled way of writing code. e.g. work in a branch, require at least one (or maybe two) person to review the changes before they go in trunk. Gabor On Thu, Feb 10, 2011 at 12:29 PM, Adam Kennedy <adamkennedybac...@gmail.com> wrote: > Also, I agree in principle but I'd like to see us at something like a > 1.00 before we do it. > > Adam K > > On 10 February 2011 21:28, Adam Kennedy <adamkennedybac...@gmail.com> wrote: >> Are you volunteering to do the branch management and all the merging? :) >> >> Adam K >> >> On 10 February 2011 20:58, Gabor Szabo <szab...@gmail.com> wrote: >>> I also think we should just increase the version number to 0.82 but we >>> also have to find >>> a way for a stable branch that only sees fixes of very serious bugs. >>> >>> We should start doing that from the next binary release. >>> >>> Gabor _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
