If we want to release the demo project separated from core, it makes sense to make a JIRA project because it's easier to generate change lists. Otherwise we won't need it.
Should we be able to release the demo project separately? I think so, because we might want to create a new demo when one of the sub projects releases. Paul On Oct 24, 2011, at 4:38 PM, Bram de Kruijff wrote: > Hi Paul, > > On Mon, Oct 24, 2011 at 4:25 PM, Paul Bakker <[email protected]> wrote: >> Hey Bram, >> >> What do you mean with "provisioning to take over at some point"? Is the demo >> release going to be replaced with something else? > > Well I guess this kind of the question I have as well :) > > In it's current form the demo a hardcoded assembly one of many > possible (software/config) configurations. I'd much rather have a > provisioning based scenario where someone can just startup a launcher > with a configurable demo profile (eg. in ACE terms a demo profile > could be one or more distributions). > > I guess a demo project could still be responsible for maintaining such > distributions, but in either case it does may not have much "code" so > i am just wondering if we want to create JIRA projects for that at > this point. > > grz > Bram > >> Paul >> >> On Oct 24, 2011, at 4:14 PM, Bram de Kruijff wrote: >> >>> Hya list, >>> >>> as discussed moments ago I have just requested 2 new known projects >>> for management and storage in JIRA. I'll give an update when they are >>> created. A couple of notes: >>> >>> 1) With regard to the profile service I was not yet sure what it will >>> be exactly. Since Marcel was not in the call I decided to wait for him >>> before deciding upon a key and name. >>> >>> 2) We did not discuss the demo release, but what should we do with >>> that? on the one hand it depends on all other projects and meant to >>> be a quickstart for users. In that sense it would be logical to make >>> it a separate project with its own lifecycle and JIRA. On the other >>> hand we may not want to give it an overly formal status as we expect >>> provisioning to take over at some point. WDYT? >>> >>> regards, >>> Bram >>> _______________________________________________ >>> Amdatu-developers mailing list >>> [email protected] >>> http://lists.amdatu.org/mailman/listinfo/amdatu-developers >> >> >> _______________________________________________ >> Amdatu-developers mailing list >> [email protected] >> http://lists.amdatu.org/mailman/listinfo/amdatu-developers >> > > _______________________________________________ > Amdatu-developers mailing list > [email protected] > http://lists.amdatu.org/mailman/listinfo/amdatu-developers _______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
