Fujimoto Hisa
hisa****@fobj*****
Tue Feb 13 13:56:54 JST 2007
There're two way to continue development simply.
(a) stay on the apple-unstable for a while (until 16th April).
(b) backup the trunk, then move the apple-unstable to the trunk, soon.
current status is the (a). I think the (b) may be better. Because it
make the trunk to the only point to watch for a developer/user/watcher.
After the apple-unstable may be merged into the trunk ...
(2007/4/16)
tags/rc-1.0 tags/rc-1.1 (or 2.0?)
\ \
trunk: -----+-(b)--*---- (develop mainstream) -----*----
/ | |
(a) | |
/ | |
apple-unstable: | *----
| tags/ tags/ tags/
| r-1.0-rc0 r-1.0 r-1.0.1
| \ \ \
branches/r-1.0: |-----*---------*--------*--- (bug fix for r-1.0)
(rc = release candidate)
--
hisa
On 2007/02/10, at 13:02, Laurent Sansonetti wrote:
> Hi all,
>
> Let's discuss the 1.0 milestone plan. Hisa-san and I suggest to
> release RubyCocoa 1.0 the 16th April.
>
> To reach this milestone, here is the plan:
>
> - merge the bundle support branch to apple unstable
> - merge the IB tool to apple unstable
> - finish the documentation support
>
> Then,
>
> - copy apple unstable to trunk
> - trunk becomes the development area (adding new features, etc...)
> - apple unstable will only be bug fixes, no new feature - all changes
> will have to be introduced very carefully
>
> And finally we will use apple unstable for RubyCocoa 1.0.
>
> We have a bit more than 2 months so!
>
> Any thoughts?
>
> Laurent
> _______________________________________________
> Rubycocoa-devel mailing list
> Rubyc****@lists*****
> http://lists.sourceforge.jp/mailman/listinfo/rubycocoa-devel