On Sun, 3 Aug 2008, Frank Niessink wrote:
> 2008/8/3 Jerome Laheurte <[EMAIL PROTECTED]>:
>> No problem with not including those notes in the notes viewer, but
>> there should be a "note" column like there is an "attachment" column.
>
> Agreed.
>
>> When all domain objects will have about the same functionalities,
>> something good would be a "unified" viewer showing all of them in a
>> tree view (I think you mentionned this "outline" feature in an old
>> mail).
>
> Yes, maybe a first step would be to remove the notes viewer and
> integrated tasks and notes in one viewer. There would need to be a
> filter to hide notes of course.
I think we should still keep a viewer for each domain object and just
add a "superviewer" for all of them at once, to accomodate all tastes.
>>> Agreed. Although we can merge back changes from the Release0_70_Branch
>>> to the trunk before releasing if we want.
>>
>> You tag before merging, don't you ?
>
> Yes, I usually tag the Release and then merge the changes between that
> release and the previous release back to the trunk. But that is just a
> policy, we can create tag now ('LastMergeToTrunk) on the
> Release0_70_Branch and then merge the changes between Release0_70_1
> and LastMergeToTrunk back to the trunk. Then after 0.70.2 is released
> we would merge the changes between LastMergeToTrunk and Release0_70_2
> back to the trunk.
No problem with your usual way.
>>> I think we should do that. There's a 'experimental' package for Task
>>> Coach on Sourceforge where we can add that release. See
>>> https://sourceforge.net/project/admin/editpackages.php?group_id=130831.
>>
>> "Permission denied", I guess it's reserved to admins.
>
> I made you a 'Release technician', does that help?
It does.
> BTW, maybe it would be a good exercise if you would do the next
> release? That way we can see whether the release is not too much
> depending on me personally (you know, hit by the bus risk and such)
> and that all necessary files are under version control.
Okay. I'll need some more info:
* On which distro do you build the various Linux packages ? I known I
had to install Fedora 8 to build its RPM, and I have also a VM with
Ubuntu installed, will that be enough ?
* What exact version of Python and wxPython do you use for Windows
packaging ? If I use a different one, it may introduce
version-specific bugs that may be hard to track...
* Is the "Release steps" list in release.py exhaustive ?
The "upload web site" step will still need you since I don't have your
password for Chello.
If I don't encounter too much problems, I'll probably make the release
today.
