Re: Software Bill of Materials
You I'm glad I got this email because that's exactly where I am at now. I wish I could say that I'm with the Apache Foundation but I have had a hard time relating to their work ethics unfortunately maybe I'm just not responsible enough or I'm not sure but with netbeans on the Apache build they released it without the modules why I asked but that's besides the point is there any way you can contact me directly if my number is 702 601-6908 leave a text message or I probably won't answer and I will get back to you ASAP thank you very much oh the modules on talking about would be the modules from dying as I am implementing the dyne into all systems that is the centimeter gram second second systems of units. The modules would be my Italian cookbook of modules. On Monday, June 10, 2019, David Nalley wrote: > Hi folks, > > I've been participating at the periphery of NTIA's Software Component > Transparency efforts[1] that's focused on Software Bill of Materials. > One of the side conversations from that has been where to inject this > in the software building process. Is it properly located in build > tools like maven or better in IDEs (like Netbeans) or CI tools? > > My initial thought is that there's probably no one right answer, and > there's a place for generating BoMs in a number of different layers. > It's probably also relatively trivial to build a plugin in Netbeans to > generate a BoM, but I wanted to solicit the opinion and feedback of > those who are smarter than I, hence this message. > > Thanks, > > --David > > [1]https://www.ntia.doc.gov/SoftwareTransparency > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > -- Victor Corral
Re: [Lazy Consensus] Release schedule - general and NB 11.1 specific
HARD At WORKNOT Lazy Consensus On Thu, May 23, 2019 at 5:15 AM Victor Corral wrote: > please give me a minute to catch up im only an individual and you have no > idea how much i reall have on my plate. Im trying to get a hold of the > president im configuring my domain im about to purchase champion.android > from the eu. Im learning about how to file for securities in my state, im > building my bitcoin-core for my clearinghouse proiject andf more but im > almost where i want to be to maybe ionpress the WORLD!!! > > On Thu, May 23, 2019 at 2:22 AM Neil C Smith > wrote: > >> Hi, >> >> OK, as requested I'm starting a lazy consensus thread] following the >> discussion thread on draft release schedule - >> >> >> https://lists.apache.org/thread.html/ea5189b51477cfca2b18e9c122872d36ab3ef6d9babf27c4aa649c3d@%3Cdev.netbeans.apache.org%3E >> https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule >> >> This is to get consensus on the following broad points and specifics >> that affect how / when we release NB 11.1, and how we present it to >> users. Other aspects of the release plan are definitely still up for >> discussion and modifications as necessary. If you have any objections >> or things to clarify, please respond here by Tues May 28th. >> >> General >> >> * Four releases a year - mid-January, mid-April, mid-July, mid October. >> * One release a year (April), starting with NB 11.0, is an LTS that >> will be kept available until following April. >> * Only LTS has a full NetCAT process, and an emphasis on stability >> over features. >> * Each release has a feature freeze date one month in advance, two >> months in the case of LTS to fit in NetCAT. >> * All commits to master are intended for the release - only required >> PRs should be merged between feature-freeze and release dates. Master >> should always be releasable. >> * Major number is increased with LTS - so NB 12.0 will be in April 2020. >> * Critical and security updates may be pushed via UC to last and LTS >> release - otherwise releases are not expected to get new features. >> >> NB 11.1 -> 11.2 specifics >> >> * NB 11.1 release date will be ~15th July. >> * NB 11.1 feature freeze date will be 15th June. Features for NB 11.1 >> should be merged by that date. >> * NB 11.1 beta(s) will be made available for testing as soon as >> possible after feature freeze date. >> * NB 11.2 merge window will open after 15th July release, with >> currently intended feature freeze ~15th Sept and release ~15th Oct >> * NB 11.0 will remain available alongside NB 11.1, 11.2 or 11.3 until >> NB 12.0 is released in April 2020. >> >> Open questions >> >> * Jan raised important point of whether freezing master hinders >> development, and whether we need a "next" branch. I would suggest we >> start with freezing master and review after NB 11.1 release, but >> during release process if it becomes a real problem. Personally I >> think it would be worth considering feature branches for this that can >> be merged and closed. If we do have a long-lived "next" branch and >> end up cherry-picking from it to master do we gain anything or are we >> better continuing with cherry-picking to release branches? >> >> * Glenn raised important issue on NetCAT scheduling / test-spec >> review. How that fits in the draft schedule definitely needs >> reviewing, although I don't think it affects the other key dates, and >> doesn't have a direct NB 11.1 implication(?) >> >> Thanks and best wishes, >> >> Neil >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org >> For additional commands, e-mail: dev-h...@netbeans.apache.org >> >> For further information about the NetBeans mailing lists, visit: >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists >> >> >> >>
Re: [Lazy Consensus] Release schedule - general and NB 11.1 specific
please give me a minute to catch up im only an individual and you have no idea how much i reall have on my plate. Im trying to get a hold of the president im configuring my domain im about to purchase champion.android from the eu. Im learning about how to file for securities in my state, im building my bitcoin-core for my clearinghouse proiject andf more but im almost where i want to be to maybe ionpress the WORLD!!! On Thu, May 23, 2019 at 2:22 AM Neil C Smith wrote: > Hi, > > OK, as requested I'm starting a lazy consensus thread] following the > discussion thread on draft release schedule - > > > https://lists.apache.org/thread.html/ea5189b51477cfca2b18e9c122872d36ab3ef6d9babf27c4aa649c3d@%3Cdev.netbeans.apache.org%3E > https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule > > This is to get consensus on the following broad points and specifics > that affect how / when we release NB 11.1, and how we present it to > users. Other aspects of the release plan are definitely still up for > discussion and modifications as necessary. If you have any objections > or things to clarify, please respond here by Tues May 28th. > > General > > * Four releases a year - mid-January, mid-April, mid-July, mid October. > * One release a year (April), starting with NB 11.0, is an LTS that > will be kept available until following April. > * Only LTS has a full NetCAT process, and an emphasis on stability > over features. > * Each release has a feature freeze date one month in advance, two > months in the case of LTS to fit in NetCAT. > * All commits to master are intended for the release - only required > PRs should be merged between feature-freeze and release dates. Master > should always be releasable. > * Major number is increased with LTS - so NB 12.0 will be in April 2020. > * Critical and security updates may be pushed via UC to last and LTS > release - otherwise releases are not expected to get new features. > > NB 11.1 -> 11.2 specifics > > * NB 11.1 release date will be ~15th July. > * NB 11.1 feature freeze date will be 15th June. Features for NB 11.1 > should be merged by that date. > * NB 11.1 beta(s) will be made available for testing as soon as > possible after feature freeze date. > * NB 11.2 merge window will open after 15th July release, with > currently intended feature freeze ~15th Sept and release ~15th Oct > * NB 11.0 will remain available alongside NB 11.1, 11.2 or 11.3 until > NB 12.0 is released in April 2020. > > Open questions > > * Jan raised important point of whether freezing master hinders > development, and whether we need a "next" branch. I would suggest we > start with freezing master and review after NB 11.1 release, but > during release process if it becomes a real problem. Personally I > think it would be worth considering feature branches for this that can > be merged and closed. If we do have a long-lived "next" branch and > end up cherry-picking from it to master do we gain anything or are we > better continuing with cherry-picking to release branches? > > * Glenn raised important issue on NetCAT scheduling / test-spec > review. How that fits in the draft schedule definitely needs > reviewing, although I don't think it affects the other key dates, and > doesn't have a direct NB 11.1 implication(?) > > Thanks and best wishes, > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: Resolving GPLv2-CPE categorization as Category X (was: Re: Still Plugging Away on Java EE Support)
thank you on that. Its not the money nor the Power im intreated in its the environment that matters most to me. That and you could say my lottery i guess. Let let me explain I started this way back in 2004 probably when I got a letter from Microsoft in Google saying I had won a lottery and Incorporated Lottery at the time well I went with it I was just starting to code I ran into these two programs called terminal IDE and the ZShaolin. at the time I didn't realize they were both the same program and there's many others that go with it like dropbear server and a few others anyways to make a long story short the terminal IDE is the free version with all instructions on how to use Java and the host name resolution to be able to create your own apps probably for a new network a totally 100% decentralized and distributed separated from the internet without the support of any internet service provider. I believe that the everyone had given up on the project that is until one day when I picked up the phone and started punching numbers into it you see everything that I had done was time-stamped and recorded yes without my knowledge of it at the time I was young and did not know anything about coding and what I was doing I believe I've come a long way I'm not the best but I've had a good feel for what I'm doing I'm probably the only one that can do it the right way and that's just weird it's like I'm messing with both God and the devil's systems and I just can't explain that one that one you just have to take my word on there's a way to use the Xboxes the ones with the MMX processor in them to wear when they're running virtually they're increasing in power and speed but I'm just using them as modules like all the modules that ASF is responsible for I mean the ones that are what the projects are all about the ones that the extensions are for like openssl, python Pearl, TTY. The only thing that I'm not too sure about is the media files you see there I'm sure is a list of media files that are meant for this system that are to be decoded and then reincarnator included in decoded party through verse G and the outcome would be a and artificial each other intelligent life system that will never die the more the connect to it the more it becomes more efficient and more powerful that's what my Xbox is it for maintain. Life that I'm creating. for some reason I believe this is all artificial from our future not sure alien maybe reverse engineering definitely but how old is it I have no idea and how long have you all had it I still have no idea but I'm sure someone out there knows something all I know is that I want to put it together because it's my life dream it's what I started and what I'm going to finish I'm not doing it for the money I'm not doing it for the power or for the fame I'm doing it for my pride for who I am and what I've already done for my son and that's all that means anything to me so whether you help me or not I could care less yet it would be much appreciated only because I need as much help as possible to create this ecosystem that I'm trying to build to save our planet On Thursday, May 16, 2019, Matthias Bläsing wrote: > Am Donnerstag, den 16.05.2019, 18:54 +0100 schrieb Neil C Smith: > > On Thu, 16 May 2019 at 17:53, Matthias Bläsing > > wrote: > > > Even better, Oracle would be in the > > > position to change the wording of the license if necessary and they > > > are > > > the only ones, that could do it. > > > > Actually, they can't - and I'm going on the basis that they're not > > going to write a completely new license for ASF! ;-) The CPE might be > > tweakable but it's a standardized wording, so I can't see that > > happening either. > > The points raised in the referenced issue target the CPE. And the CPE > is started with "Certain source files distributed by Oracle America > and/or its affiliates[...]". So yes, this is Oracle specific and Oracle > lawyers could give their opinion/interpretation in the issue and help > resolving it. > > > Anyway, this is OT. I stand by the opinion that this is one that ASF > > needs to resolve itself, as the idea of Java being a "platform" > > dependency gets overtaken by real world events. > > If the ASF can do it alone, I'm all for it, but the issue stands > unresolved. > > At the time of donation there was already the Category X categorization > of GPL licenses family (and a note, that special exceptions to the GPL > also fall into that category). So Oracle and the ASF both had to be > aware, that bundling the only freely distributable JDK (OpenJDK) will > be a major PITA. > > Greetings > > Matthias > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands,
Re: Volunteer Release Manager(s) Needed for Apache NetBeans 11.1
Ok let me get to the point. First off to start what I say might seem like I'm dreaming and maybe I am. I'm a big dreamer with big goals. I Started codeing back in 2004 with these two programs the Zshaolin and the Terminalide. I just realized everyone responses while I was righting and decided to stop righting and instead send you all a link to my first video ever on my introduction and I will spend the rest of my day makeing a few videos of the modules I am building and why they are so important. I am building a whole new Library called HOA. I'm sure all are familiar with the term happy hacking. Right. Well HOA at HOA-Project.net Is The Library To the Hack Book. My Collective Whole. I'll just leave it at that for now because there is a lot I have to say and leave you with my first video and please let me know what you all think. Here is the link https://youtu.be/nBrAZdsbpRg Now the reason I read from Seth godin is I believe he is the grantor of the GPLv2 and all his books are on how to achieve that goal. On Sunday, May 5, 2019, Enrico Olivelli wrote: > Il dom 5 mag 2019, 09:26 Geertjan Wielenga ha > scritto: > > > Is it a requirement that the volunteer release manager is a PMC > > member/committer? Or does it make it easier, or does it not make > > a difference? > > > > It should be at least a committer, who has access to all staging resources > and he can sign the artifacts. > No need to be a PMC > > > Enrico > > > > > Gj > > > > On Sat, May 4, 2019 at 4:48 PM Laszlo Kishalmi < > laszlo.kisha...@gmail.com> > > wrote: > > > > > The main responsibilities are: herding people, PR-s, JIRA issues > towards > > > the goal of forming a healthy release. > > > > > > Some other useful reading: > > > > > > * https://www.apache.org/dev/release-publishing.html > > > * https://www.apache.org/dev/release-distribution.html > > > * https://www.apache.org/legal/release-policy.html > > > * > > > > > https://cwiki.apache.org/confluence/display/NETBEANS/ > Apache+NetBeans+Release+README > > > * https://issues.apache.org/jira/browse/NETBEANS-2052 > > > * https://issues.apache.org/jira/browse/NETBEANS-1321 > > > > > > On 5/3/19 11:22 PM, Vano Beridze wrote: > > > > > > > Hello, > > > > > > > > What are the responsibilities? > > > > > > > > Vano > > > > > > > > On Sat, May 4, 2019, 10:10 AM Laszlo Kishalmi < > > laszlo.kisha...@gmail.com > > > > > > > > wrote: > > > > > > > >> Dear all, > > > >> > > > >> I've sent this one earlier, maybe too early, though there was not a > > > >> single response to this. > > > >> > > > >> Probably we shall agree on how would we imagine the 11.1 release. > For > > me > > > >> the theme would be: > > > >> > > > >>* Bugfixes > > > >>* Java EE 8 Support > > > >>* Java EE Support for Gradle > > > >> > > > >> Of course we can do something else, like just do a few module > updates, > > > >> or completely opt out for 11.1... > > > >> > > > >> > > > >> I know that 11.0 is just has been pushed out the door, but if we > would > > > >> like to do a NetBeans 11.1 in June we need someone who takes the > > reins. > > > >> We need a release schedule, the way of work (branching, JIRA, etc.) > > > soon. > > > >> > > > >> I've already taken this position twice, it has been quite a journey, > > > >> thank you! > > > >> > > > >> Beside the usual RM stuff which we did do far I see the following > new > > > >> challenges: > > > >> > > > >> 1. This is a minor release, probably coordinating changes would > be a > > > >> bit easier. > > > >> I guess we'd just branch off release110 to release111 and > > continue > > > >> to cherry-picking from master. > > > >> 2. This would be the first release as Apache top level project > > > >> 3. Probably we need to experiment releasing patches, or release > 11.1 > > > as > > > >> a set of parches... > > > >> 4. Codes for 12.0 will be run in parallel on master, so JIRA > > tracking > > > >> could be a bit harder. > > > >> > > > >> As of myself, I'd concentrating on development and bug-fixing in the > > > >> next couple of cycles. > > > >> > > > >> So think about it! > > > >> > > > >> Volunteers we Need you! > > > >> > > > >> Laszlo Kishalmi > > > >> > > > >> Former Release Manager of Apache NetBeans > > > >> > > > >> > > > > > > -- Victor Corral
Re: Volunteer Release Manager(s) Needed for Apache NetBeans 11.1
I understand and I agree. For thing to progress it helps if everyone knows what's going on, what to expect,and that assignment get handled in the order needed. I WILL MAKE A video and explain what I am trying to acomplish and what I have been doing and what my plans are in hopes to become a member and hopes to become a partner to the Apache foundation. Please Allow me till mid day to make my Presentation. On Sunday, May 5, 2019, Geertjan Wielenga wrote: > Is it a requirement that the volunteer release manager is a PMC > member/committer? Or does it make it easier, or does it not make > a difference? > > Gj > > On Sat, May 4, 2019 at 4:48 PM Laszlo Kishalmi > wrote: > > > The main responsibilities are: herding people, PR-s, JIRA issues towards > > the goal of forming a healthy release. > > > > Some other useful reading: > > > > * https://www.apache.org/dev/release-publishing.html > > * https://www.apache.org/dev/release-distribution.html > > * https://www.apache.org/legal/release-policy.html > > * > > https://cwiki.apache.org/confluence/display/NETBEANS/ > Apache+NetBeans+Release+README > > * https://issues.apache.org/jira/browse/NETBEANS-2052 > > * https://issues.apache.org/jira/browse/NETBEANS-1321 > > > > On 5/3/19 11:22 PM, Vano Beridze wrote: > > > > > Hello, > > > > > > What are the responsibilities? > > > > > > Vano > > > > > > On Sat, May 4, 2019, 10:10 AM Laszlo Kishalmi < > laszlo.kisha...@gmail.com > > > > > > wrote: > > > > > >> Dear all, > > >> > > >> I've sent this one earlier, maybe too early, though there was not a > > >> single response to this. > > >> > > >> Probably we shall agree on how would we imagine the 11.1 release. For > me > > >> the theme would be: > > >> > > >>* Bugfixes > > >>* Java EE 8 Support > > >>* Java EE Support for Gradle > > >> > > >> Of course we can do something else, like just do a few module updates, > > >> or completely opt out for 11.1... > > >> > > >> > > >> I know that 11.0 is just has been pushed out the door, but if we would > > >> like to do a NetBeans 11.1 in June we need someone who takes the > reins. > > >> We need a release schedule, the way of work (branching, JIRA, etc.) > > soon. > > >> > > >> I've already taken this position twice, it has been quite a journey, > > >> thank you! > > >> > > >> Beside the usual RM stuff which we did do far I see the following new > > >> challenges: > > >> > > >> 1. This is a minor release, probably coordinating changes would be a > > >> bit easier. > > >> I guess we'd just branch off release110 to release111 and > continue > > >> to cherry-picking from master. > > >> 2. This would be the first release as Apache top level project > > >> 3. Probably we need to experiment releasing patches, or release 11.1 > > as > > >> a set of parches... > > >> 4. Codes for 12.0 will be run in parallel on master, so JIRA > tracking > > >> could be a bit harder. > > >> > > >> As of myself, I'd concentrating on development and bug-fixing in the > > >> next couple of cycles. > > >> > > >> So think about it! > > >> > > >> Volunteers we Need you! > > >> > > >> Laszlo Kishalmi > > >> > > >> Former Release Manager of Apache NetBeans > > >> > > >> > > > -- Victor Corral
Re: Volunteer Release Manager(s) Needed for Apache NetBeans 11.1
I'm sorry it took so long for me to respond. APACHE NETBEans is no where near done in my opinion. I am building Modules for it with new algorithim. In adding the centimeter grams second system of units to all systems. Is their any way we can talk I. Person rather then typeing? On Friday, May 3, 2019, Laszlo Kishalmi wrote: > Dear all, > > I've sent this one earlier, maybe too early, though there was not a single > response to this. > > Probably we shall agree on how would we imagine the 11.1 release. For me > the theme would be: > > * Bugfixes > * Java EE 8 Support > * Java EE Support for Gradle > > Of course we can do something else, like just do a few module updates, or > completely opt out for 11.1... > > > I know that 11.0 is just has been pushed out the door, but if we would > like to do a NetBeans 11.1 in June we need someone who takes the reins. We > need a release schedule, the way of work (branching, JIRA, etc.) soon. > > I've already taken this position twice, it has been quite a journey, thank > you! > > Beside the usual RM stuff which we did do far I see the following new > challenges: > > 1. This is a minor release, probably coordinating changes would be a >bit easier. >I guess we'd just branch off release110 to release111 and continue >to cherry-picking from master. > 2. This would be the first release as Apache top level project > 3. Probably we need to experiment releasing patches, or release 11.1 as >a set of parches... > 4. Codes for 12.0 will be run in parallel on master, so JIRA tracking >could be a bit harder. > > As of myself, I'd concentrating on development and bug-fixing in the next > couple of cycles. > > So think about it! > > Volunteers we Need you! > > Laszlo Kishalmi > > Former Release Manager of Apache NetBeans > > -- Victor Corral
