[V3dot10] And to 3.10

[Milan Zimmermann]

On 2007 January 22 05:39, Keith Hodges wrote:
> Milan Zimmermann wrote:
> > On 2007 January 21 12:49, Keith Hodges wrote:
> >> http://squeak310.pbwiki.com/From39To391MantisFixes
> >> and
> >> http://squeak310.pbwiki.com/From39To391MantisFixes-stable
> >
> > Keith, this is a great list with priorities. What is the suggested
> > process of a fix making it from the first list (From39To391MantisFixes)
> > to the other (From39To391MantisFixes-stable) - what action is required? I
> > speculate that a
>
> oops I meant
>
> http://squeak310.pbwiki.com/From39To391MantisFixes
> and
> http://squeak310.pbwiki.com/From39To391MantisFixes-unstable

yes

>
> The process is, that you put code that is needed to harvest the bug into
> the unstable page, until you are sure it actually works. This is because
> you dont want to break everyone elses stuff.

ok that sounds good. If a harvester is deciding whether to accept a fix, he 
may first load the change into yet another "personal" image, where he would 
run the automated tests but perhaps also some manual tests. When it looks 
good the fix would be moved to unstable, I think that is covered by your note 
below "You can have as many working areas as you wish".

Thanks Milan

PS: For 3.10, would the stable/unstable still apply? It seems there may only 
be 1 image .. appologize for all these process questions

>
> When tested and you are happy with it, you move it to the other one (the
> stable) branch. You should only move 'stable' stuff to the stable branch.
>
> In other words, -unstable is a working area, and stable is the
> publishing results area. You can have as many working areas as you wish.
>
> does that help explain things
>
> Keith
>
> > harvester (ideally a corresponding team member) will validate the fix and
> > move it to the "stable" list? I cannot connect to Impara, but in general,
> > it seems that would be a duplication of what Mantis should do: Move an
> > item through a lifecycle such that
> > "Open->Reviewed->Approved->Applied->Closed" (completely speculating on
> > those lifecycle statuses).
> >
> > Milan
> >
> >> There are other places that mantis fixes are used in this process, but
> >> those are the main ones.
> >>
> >> This captures the information as to what fixes are ready and desired,
> >> and gives us a common platform for testing those fixes a.s.a.p. The
> >> scripts that are generated from these pages can also be reused in
> >> whatever future form 3.10 may take.
> >>
> >> If you have any questions about anything please feel free to ask.
> >>
> >> Keith
> >>
> >>
> >>
> >>
> >>
> >> ___________________________________________________________
> >> All new Yahoo! Mail "The new Interface is stunning in its simplicity and
> >> ease of use." - PC Magazine http://uk.docs.yahoo.com/nowyoucan.html
> >> _______________________________________________
> >> V3dot10 mailing list
> >> V3dot10 at lists.squeakfoundation.org
> >> http://lists.squeakfoundation.org/mailman/listinfo/v3dot10
> >
> > _______________________________________________
> > V3dot10 mailing list
> > V3dot10 at lists.squeakfoundation.org
> > http://lists.squeakfoundation.org/mailman/listinfo/v3dot10
>
> ___________________________________________________________
> All new Yahoo! Mail "The new Interface is stunning in its simplicity and
> ease of use." - PC Magazine http://uk.docs.yahoo.com/nowyoucan.html
> _______________________________________________
> V3dot10 mailing list
> V3dot10 at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/v3dot10