[Gambas-user] Beta PPA

[Sebastian Kulesz]

Actually, it is compiled using the latest code from the 3.6 branch, so code
committed to /trunk and not backported to /branches/3.6 should not
interfere at all. I can't use /trunk from a few weeks because there can be
breaking changes which could brake the build anytime. Only the code you
backport is included, and a new commit to the 3.6 branch triggers a new
build.
On Oct 30, 2014 2:49 PM, "Benoît Minisini" <gambas at ...1...>
wrote:

> Le 30/10/2014 18:31, Tobias Boege a écrit :
> > On Thu, 30 Oct 2014, Sebastian Kulesz wrote:
> >> Hey!
> >>
> >> As i mentioned when Gambas 3.6 was released, i had the idea of making a
> >> beta PPA for those of you who needed bugfixes backported immediately,
> but
> >> couldn't use the Daily PPA because you also needed some kind of
> stability.
> >>
> >
> > So the beta repository is the latest stable version plus bugfixes? How do
> > you distinguish between new-feature commits and bugfix commits from
> trunk?
> >
> > I look specifically at commit r5778 as an example which has various
> items,
> > and at least two of each type:
> >
> >
> --8<-----------------------------------------------------------------------
> > * BUG: Fix possible bugs when [...]
> > * BUG: Really erase old elements [...]
> > * OPT: Current and the enumerators [...]
> > * OPT: Remove workaround code [...]
> > * NEW: Expose List.Current as a [...]
> > * NEW: List.Value is what [...]
> > * NEW: Add List.Current.Index and [...]
> > * NEW: Add a List.AutoNormalize property [...]
> > * NEW: Add List.MoveTo() to point Current [...]
> > * NEW: List.Current.Is{First,Last,Valid} [...]
> >
> --8<-----------------------------------------------------------------------
> >
> > Would this be picked for beta from your system or not? How would I make
> > commits that play together with your system?
> >
> > And what happens when a bugfix commit builds on top of a new feature,
> i.e.
> > can't be applied?
> >
> > Regards,
> > Tobi
> >
>
> Good questions.
>
> For example, I'm currently backporting bugfixes that are "backport-able"
> to /branches/3.6, and when I'm done I'm making a 3.6.1 from it.
>
> I suggest that "beta" should be a development revision a few weeks in
> the past (for example) that has no big problem.
>
> Regards,
>
> --
> Benoît Minisini
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Gambas-user mailing list
> Gambas-user at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gambas-user
>