- Do we need to define facets as API - what attributes, behavior should be considered API? - Possibly similar to plugin extension points where everything considered API - Chuck to track down policy. - We need to better define our policy on adding features in maintenance release - Is feature patch a viable solution for adopters? - Neil - this change will create project compatibility issues (3.2.5 projects can't be shared into 3.2.4 workspace)
Kaloyan - Continue polling - discuss results on Thursday's call' - Should we put a stake in the ground mandating when we need to see some progress in educating our committers? - investigate a subproject that could "pilot" a git repo feeding into our overall PDE build - More discussion on CVS - GIT transition - should replace CVS feature for feature
Neil - Many small problems found - subtle changes in behavior - not clear issues are adopter usage or platform bugs. - Need to track across WTP - propose a whiteboard tag for finding 4.x issues(both WTP and platform)
webtool.website Progress from tracking bug
Progress moving WTP 3.4 builds "officially" to 4.2 platform as the default. Tracking progress of special R4.2 sniff test Carl continues to work on 4.2 builds to get the wtp zips published, and ready to change order and frequency of both 3.8 and 4.2 builds
Back to meeting list.
Please send any additions or corrections to Chuck Bridgham.
Back to the top