The releases are complete in their release directories (set up the same way
throughout all projects). The problem is rather if you have in-between
versions that you would want to checkout but copying the source at release
time wouldn't solve that.
The modules are separate because that is the most convenient way to manage
user access and have separate commits lists.
/Linus
On Tue, Apr 27, 2010 at 4:52 PM, Bob Tarling <[email protected]> wrote:
> Linus said
>
> On 27 April 2010 15:39, Linus Tolke Tigris <[email protected]> wrote:
>
>> The merging from trunk to branch, I have to do more or less manually so I
>> can easily avoid doing it in any of the projects (just as easily as it was
>> to forget the merging for some of the projects that I did in the Beta2
>> version ;-).
>>
>> If there are patches in the argouml-java project that are to be included
>> while others are not, that's when it is more work to keep track of the
>> version numbers.
>>
>>
>
> Should we not bring the argouml subprojects for stable modules that we
> package into a release into the main repository for ArgoUML?
>
> Otherwise it is difficult to go back to a specific revision number and have
> everything in a release complete.
>
> Why still have these modules separate? The previous arguments had been
> mostly around making sure dependencies are controlled but that is solved
> now.
>
> Regards
>
> Bob
>
>
------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2597075
To unsubscribe from this discussion, e-mail:
[[email protected]].
To be allowed to post to the list contact the mailing list moderator, email:
[[email protected]]
