- The "merge" isn't a merge, but a switch
- Please refrain from svn checkins until this is finished
- I'll send another note, when it's done
2) Thereafter the trunk remains feature-frozen
- no new feature checkins please
- bugfixes and such welcome
- examples and benchmark updates welcome (I'm pretty sure that some
examples are still using old calling conventions)
- non-trivial PASM examples should be rewritten in PIR
- updates to PLATFORMS, test results are wanted too
3) Release will follow at the weekend
Thanks,
leo
It's none of my business I know, but why not give the release a more
realistic number (e.g. 0.7.0)?
People tend to extrapolate that if it took 5 years to get to 0.2.3 then
it will take another 16 years to get to version 1.0.
Regards,
Roger Browne
Release number and name aren't decided yet. But I can image that it'll
be numbered 0.3.0
> Regards,
> Roger Browne
leo
If you have any checkouts of the leo-ctx5 branch, you will need to
switch them to trunk
cd parrot-checkout-of-leo-ctx5-branch
svn switch https://svn.perl.org/parrot/trunk/
-R
>
> 1) I'll start "merging" branches/leo-ctx5 back to trunk soon.
>
> - The "merge" isn't a merge, but a switch
> - Please refrain from svn checkins until this is finished
Step 1) finished. All the merits and thanks belong to Robrt and clkao.
Robert did the actual work and clkao provided hints as well as the base
for the merge: svk.
Thanks folks - I would have been lost.
If you have a recent checkout of branches/leo-ctx5 just use "svn
switch" to switch the branch back to trunk.
If not - "svn co" the trunk as usual. The branch is probably gone
already.
Reminder: the trunk remains feature-frozen.
Bugfixes, docu upates, fixes to examples and so on are welcome,
thanks again all,
leo
> 3) Release will follow at the weekend
I'll start the release procedure RSN. Please no more svn checkins at
all.
leo