Hi Julian
I think a higher frequency release is not an issue.
You just need to have enough PMC members to vote.
Compiling, LICENSE, sign checks are the key, instead, the feature tests and
whether you are releasing a stable release, that is PMC's call.
The minimal time requirement is only 3 days to
Hi, Kerry, I too think Apache would be a good home for Brackets. As you may
know, each Apache project has a Project Management Committee (PMC) that is
responsible for it. You, as a Brackets community member, are ideally placed
to find a half dozen other Brackets users who should be willing to be th
I am sure that we all have heard that Adobe is no longer interested in
maintaining Brackets. I am looking at Apache to adopt the Brackets
Project and think it would be a good fit for your organization. I think
that it would be a great time for you to strike a deal with Adobe to
takeover the pro
It is community over code in Apache. By having people, beyond tests, verify
your releases, you build a community rather than a bunch of releases. The
releases of your prohect are not the primary point here. It’s about
building a community which means having at least three people to verify
your rele
The Arrow-Rust modules are much smaller than NetBeans. They are
libraries and can be continuously verified by automated tests, and
therefore, from a software quality standpoint, it is possible to
release at any time. But, to this point, the release cadence has been
artificially slowed to about 3 mo
Speaking as PMC of Apache NetBeans, we have a new release every quarter.
That’s about as much as one can do for a large project. If you find the
requirement to have three people to verify your releases onerous, are you
saying that so far less than three people have been verifying your releases
thus
Does anyone have any resources/suggestions for making the Apache
release process work smoothly for a community whose culture expects
very frequent releases?
Some background. I am an ASF member and PMC member of Arrow. I am not
very active in development, but am doing my best to oversee the
project
Recently, a user contributed a pull request for Accumulo to add
.github/CODE_OF_CONDUCT.md
I can see this being useful so that the ASF Code of Conduct is
presented in the GitHub UI. However, I don't think every project needs
to do this.
I propose ComDev work with INFRA to create
https://github.com
Hi All
We have seen a trend where many of our CFP submissions come in during the final
week and especially the last few days..and this year is no exception :-)
This is a final reminder that the CFP for both ApacheCon@Home and ApacheCon
Asia will be closing on Monday, May 3rd, 2021 at 8:00 AM (
On Sat, 1 May 2021 at 08:40, Javi Roman wrote:
>
> Sebb, that's a good idea, the wiki space could be a beginning.
>
> I'm going to request (INFRA) a Wiki space for this initiative:
> https://cwiki.apache.org/confluence/display/HEALTH/Home
>
> and a mailing list for discussing:
> hea...@apache.org
Sebb, that's a good idea, the wiki space could be a beginning.
I'm going to request (INFRA) a Wiki space for this initiative:
https://cwiki.apache.org/confluence/display/HEALTH/Home
and a mailing list for discussing:
hea...@apache.org
Please let me know if I have your support to request these re
11 matches
Mail list logo
