Lets leave this till nearer the time. I'm starting a new work project that is eating into my own time for learning so I'm not 100% sure what my input will be so far.
Just go for your standard release procedure for now and if someone wants to continue development work we can think about branch if and when it needed. For non-supported modules that are released only for testing I still don't see the need for a branch however as that's your decision. Regards Bob On 11 November 2010 06:09, Linus Tolke Tigris <[email protected]> wrote: > Hello Bob! > (I wrote another answer to this yesterday morning but that was apparantly > lost somewhere.) > The root problem is that we usually lock up the trunk for a very long time > while doing the alpha/beta release schedule. We noticed that as a problem > also last time as I recall. > The solution would then be to reduce the time when trunk is locked by making > a release branch earlier, my suggestion is the first beta. This means extra > work for fixes done in the beta branch since they need to be applied twice. > This will reduce the time when the trunk is restricted to just the alpha > phase. > Would this be a good solution? Would this solve the problem for the state2 > and activity2 work? > /Linus > > > Den 9 november 2010 09.34.33 UTC+1 skrev Bob Tarling > <[email protected]>: >> >> Yes but they do not operate unless in UML2 mode. When running in UML2 >> mode the user gets a clear warning that the code is not stable. >> >> Regards >> >> Bob >> >> On 9 November 2010 06:13, Linus Tolke Tigris <[email protected]> wrote: >> > To be clear! >> > Both state2 and activity2 are included in the release. Changing them >> > will >> > change the delivered contents of the release. >> > I will get back with a suggested solution. >> > /Linus >> > >> > >> > >> > 2010/11/8 Linus Tolke Tigris <[email protected]> >> >> >> >> Hello Bob! >> >> I would have preferred, if we should have two conflicting quality >> >> measures >> >> in the release, to have two distinct items released and only release >> >> the one >> >> without the release. >> >> In any case, I am sure we can handle this and I will try to be explicit >> >> when doing the announcements. >> >> /Linus >> >> >> >> Den 7 november 2010 12.31.55 UTC+1 skrev Bob Tarling >> >> <[email protected]>: >> >>> >> >>> I'm hoping I can find time getting back to the UML2 diagrams for state >> >>> and activity soon. >> >>> >> >>> Unless someone states otherwise I am assuming it is fine to commit to >> >>> those modules at any time during our approaching stable release phase. >> >>> >> >>> With issue 6161 >> >>> (http://argouml.tigris.org/issues/show_bug.cgi?id=6161) in mind it >> >>> would seem dumb to hard code everything for those diagrams with the >> >>> intention of reworking them later. So before I continue work on those >> >>> diagrams I will be reimplementing what is already there around some >> >>> XML definitions and will then continue with completing the diagrams on >> >>> those new principles. The lessons learned can then be taken into other >> >>> diagrams as they are split out into their own modules.. >> >>> >> >>> I hope Michiel may be able to spare me some time when it comes to >> >>> implementing the notations. >> >>> >> >>> Regards >> >>> >> >>> Bob. >> >>> >> >>> ------------------------------------------------------ >> >>> >> >>> >> >>> http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2679668 >> >>> >> >>> 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]] >> >> >> > >> > >> >> ------------------------------------------------------ >> >> http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2680388 >> >> 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]] > > ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2681721 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]]
