Create new and noteworthy for Alpha2
by Max Rydahl Andersen
Hey,
First of - *many* thanks to Andre and Xavier for doing the right thing and have N&N ready for Alpha2 around codefreeze.
For the rest of you a jira is apparently needed thus I went ahead and wrote this: https://github.com/jbosstools/jbosstools-documentation/blob/563b823b98975...
Which created https://issues.jboss.org/browse/JBIDE-14268 + subtasks.
It is similar to what I and Denis over the years created manually or cloned but now it
only takes seconds vs half-hours of clicking around.
Bonus is that the subtasks contains queries for the specific components - hopefully making life easier for component leads.
Let me know if something is borked or broken in this auto-created N&N.
And btw. N&N is needed ASAP since we want to have this release out.
/max
13 years, 2 months
Code Frozen in Alpha2x branch
by Nick Boldt
Note that as it's expected that the Alpha2b respin will be the last
respin toward Alpha2, I have DISABLED all the _41 jobs.
If you need to commit anything to the 4.1.0.Alpha2x branch of any
project, please:
* open a JIRA
* attach a PR
* notify Max/Fred/Denis/myself that your PR needs review, via this list
Ideally, no one should need to fix anything in the Alpha2x branch, so
the above reminder is simply JUST IN CASE.
Cheers,
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
13 years, 2 months
please check your Alpha2 issues - too many open
by Max Rydahl Andersen
Hi,
alpha2 codefroze ~1 week ago but there are still a tons of issues set with it as fix version (many from way before
alphs2 codefreeze)
Please take a look and make sure they get triaged ASAP.
Thanks,
Max
13 years, 2 months
Please adopt the 4.1.0.Beta1-SNAPSHOT version of the JBT parent pom in your project's master branch's root pom.xml
by Nick Boldt
I've updated the parent pom in the master branch to version Beta1:
-<version>4.1.0.Alpha2-SNAPSHOT</version>
+<version>4.1.0.Beta1-SNAPSHOT</version>
-<BUILD_ALIAS>Alpha2</BUILD_ALIAS>
+<BUILD_ALIAS>Beta1</BUILD_ALIAS>
It will also use the RELEASED version of our Kepler M6 target platform:
-<TARGET_PLATFORM_VERSION>4.30.5.Alpha3-SNAPSHOT</TARGET_PLATFORM_VERSION>
+<TARGET_PLATFORM_VERSION>4.30.5.Alpha3</TARGET_PLATFORM_VERSION>
-<TARGET_PLATFORM_VERSION_MAXIMUM>4.30.5.Alpha3-SNAPSHOT</TARGET_PLATFORM_VERSION_MAXIMUM>
+<TARGET_PLATFORM_VERSION_MAXIMUM>4.30.5.Alpha3</TARGET_PLATFORM_VERSION_MAXIMUM>
*Your master branch's root pom.xml needs to use parent pom version
4.1.0.Alpha2-SNAPSHOT* if you want to automatically adopt the Beta1
suffix in your jar qualifiers for your master branch builds, and to
later pick up the forthcoming 4.30.5.Alpha4-SNAPSHOT target platform,
which will be available in May when Kepler M7 is released [1].
[1] http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#Schedule
Note too that the parent pom in the stable branch (4.1.0.Alpha2x) has
also been updated to use to use released 4.30.5.Alpha3 (Kepler M6)
target platform.
-<TARGET_PLATFORM_VERSION>4.30.5.Alpha3-SNAPSHOT</TARGET_PLATFORM_VERSION>
+<TARGET_PLATFORM_VERSION>4.30.5.Alpha3</TARGET_PLATFORM_VERSION>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
13 years, 2 months
[IMPORTANT] Changes in Default Assignee and Component lead notification
by Max Rydahl Andersen
Hi,
= Change in Jira
Since this morning all components in JBIDE and JBDS uses "Unassigned" as the default assignee for all new issues.
Component leads will still be notified about issue creation, update, resolution and reopening of issues in their component but
will no longer be the default assignee.
If you are not planning or intending to work on an issue then unassign your self; and vice versa assign your self if you are working on it.
= Reason
This change is based on the feedback/discussions at various face-2-faces and calls; there
was a feeling/concensus that it was not possible to query for issues that not yet have anyone
committed to fix or react to an issue.
This change makes that possible by making the assignee field actually useful again.
In short:
If an issue is assigned that assignee has taken on that task or been asked to take on that task.
If an issue is unassigned it is non-triaged or falling through the cracks and needs attention (similar
to when no fix version nor component set)
= Why not before ?
Previously (last year) there were no "component lead" option in notifcations; that changed a while ago and I've just not
had time to change it sooner.
Let me know if you see or experience issues, getting too many/few notifcations to keep on top of your component(s).
Thank you,
Max
13 years, 2 months
